Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[BUG] Explaination missing of what Persistent/Transient mean in ResourceHealth #32472

Open
Klaas- opened this issue Feb 5, 2025 · 0 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@Klaas-
Copy link

Klaas- commented Feb 5, 2025

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/07da438f8dc690946b39511467744ed889434de5/specification/resourcehealth/resource-manager/Microsoft.ResourceHealth/stable/2024-02-01/ResourceHealth.json

API Spec version

2024-02-01

Describe the bug

Within the rest-api spec of the Resource Health there is a reasonChronicityTypes. It does list the possible values as "Persistent" and "Transient" but does not explain what those mean. From testing I would say after a state change it will remain in "Transient" state for 20 minutes, afterwards if there are no further changes it will change to "Persistent". I guess you should note that in description of the values.

Expected behavior

actual behavior + descriptions of that those states actually mean.

Actual behavior

            "reasonChronicity": {
              "type": "string",
              "description": "Chronicity of the availability transition.",
              "enum": [
                "Transient",
                "Persistent"
              ],
              "x-ms-enum": {
                "name": "reasonChronicityTypes",
                "modelAsString": true
              }
            },

Reproduction Steps

Read API spec, discover missing description and the strings themselves are not self-explanatory.

Environment

No response

@Klaas- Klaas- added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Feb 5, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Feb 5, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

1 participant