ArmRollingUpgradeMonitoringPolicy Class
The policy used for monitoring the application upgrade.
- Inheritance
-
azure.mgmt.servicefabric._serialization.ModelArmRollingUpgradeMonitoringPolicy
Constructor
ArmRollingUpgradeMonitoringPolicy(*, failure_action: str | _models.ArmUpgradeFailureAction | None = None, health_check_wait_duration: str = '0', health_check_stable_duration: str = 'PT0H2M0S', health_check_retry_timeout: str = 'PT0H10M0S', upgrade_timeout: str = 'P10675199DT02H48M05.4775807S', upgrade_domain_timeout: str = 'P10675199DT02H48M05.4775807S', **kwargs: Any)
Keyword-Only Parameters
Name | Description |
---|---|
failure_action
|
The activation Mode of the service package. Known values are: "Rollback" and "Manual". |
health_check_wait_duration
|
The amount of time to wait after completing an upgrade domain before applying health policies. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. default value: 0
|
health_check_stable_duration
|
The amount of time that the application or cluster must remain healthy before the upgrade proceeds to the next upgrade domain. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. default value: PT0H2M0S
|
health_check_retry_timeout
|
The amount of time to retry health evaluation when the application or cluster is unhealthy before FailureAction is executed. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. default value: PT0H10M0S
|
upgrade_timeout
|
The amount of time the overall upgrade has to complete before FailureAction is executed. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. default value: P10675199DT02H48M05.4775807S
|
upgrade_domain_timeout
|
The amount of time each upgrade domain has to complete before FailureAction is executed. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. default value: P10675199DT02H48M05.4775807S
|
Variables
Name | Description |
---|---|
failure_action
|
The activation Mode of the service package. Known values are: "Rollback" and "Manual". |
health_check_wait_duration
|
The amount of time to wait after completing an upgrade domain before applying health policies. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. |
health_check_stable_duration
|
The amount of time that the application or cluster must remain healthy before the upgrade proceeds to the next upgrade domain. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. |
health_check_retry_timeout
|
The amount of time to retry health evaluation when the application or cluster is unhealthy before FailureAction is executed. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. |
upgrade_timeout
|
The amount of time the overall upgrade has to complete before FailureAction is executed. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. |
upgrade_domain_timeout
|
The amount of time each upgrade domain has to complete before FailureAction is executed. It is first interpreted as a string representing an ISO 8601 duration. If that fails, then it is interpreted as a number representing the total number of milliseconds. |
Azure SDK for Python
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for