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
During stabilization, the handler needs to be checking if StateReason is being returned from the request. The presence of this value indicates that there was an error and that the canary did not successfully update as intended. Currently, the handler is still treating this as a successful update. This can cause CloudFormation to register a bad deployment as a successful update.
As an example, here is a canary that it not in a stable state. This should be causing CloudFormation updates to fail, but it is not:
It looks like the model JSON also needs to be updated to be able to support this, see here where it only has State.
When performing the Update (and most likely in the Create handler as well), the handler needs to check that there is no StateReason returned before considering the request successful, see here.
The text was updated successfully, but these errors were encountered:
During stabilization, the handler needs to be checking if
StateReason
is being returned from the request. The presence of this value indicates that there was an error and that the canary did not successfully update as intended. Currently, the handler is still treating this as a successful update. This can cause CloudFormation to register a bad deployment as a successful update.As an example, here is a canary that it not in a stable state. This should be causing CloudFormation updates to fail, but it is not:
It looks like the model JSON also needs to be updated to be able to support this, see here where it only has
State
.When performing the Update (and most likely in the Create handler as well), the handler needs to check that there is no
StateReason
returned before considering the request successful, see here.The text was updated successfully, but these errors were encountered: