You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I update the property HealthCheckConfig.RoutingControlArn of AWS::Route53::HealthCheck resource, the changeset is successfully deployed but the actual resource does not reflect the update.
Expected Behavior
The changes to HealthCheckConfig.RoutingControlArn is reflected to the actual resource.
Observed Behavior
The changes to HealthCheckConfig.RoutingControlArn is NOT reflected to the actual resource.
Deploy the stack to update the template. Now rc-primary and rc-secondary should be assigned one healthcheck each, but actually rc-primary still has two healthchecks and rc-secondary has none, which means the update is not reflected. (unexpected)
Other Details
No response
The text was updated successfully, but these errors were encountered:
Name of the resource
AWS::Route53::HealthCheck
Resource Name
No response
Issue Description
When I update the property HealthCheckConfig.RoutingControlArn of AWS::Route53::HealthCheck resource, the changeset is successfully deployed but the actual resource does not reflect the update.
Expected Behavior
The changes to HealthCheckConfig.RoutingControlArn is reflected to the actual resource.
Observed Behavior
The changes to HealthCheckConfig.RoutingControlArn is NOT reflected to the actual resource.
Test Cases
First, we deploy the template below:
The rc-primary routing control has two health checks assigned (expected).
And rc-secondary does not have any health check (expected).
Next, update a
RoutingControlArn
property with the following template:The diff is:
Deploy the stack to update the template. Now rc-primary and rc-secondary should be assigned one healthcheck each, but actually rc-primary still has two healthchecks and rc-secondary has none, which means the update is not reflected. (unexpected)
Other Details
No response
The text was updated successfully, but these errors were encountered: