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
Currently, the CloudFormation resource specification and the documentation do not distinguish the difference between an update operation which fully replaces a resource (including data loss) from those updates which cause some other kind of downtime (e.g a server or database reboot).
The documentation maps both of these concepts to 'Update requires: some interruption' and the resource spec maps only the fully immutable replacement operation, as does the schema currently.
We could include a schema property to signal that a property may cause downtime without data loss as a distinguishing concept.
The text was updated successfully, but these errors were encountered:
PatMyron
changed the title
Include a updateCausesDowntime semantic property
Schematize nuanced immutability (conditional resource replacement, downtime, etc.)
Mar 21, 2020
In addition to this problem with createOnlyProperties being more nuanced than being expressable in just a boolean, the same problem applies to readOnlyProperties and writeOnlyProperties as well https://twitter.com/InesParnisari/status/1327040431138299904
Currently, the CloudFormation resource specification and the documentation do not distinguish the difference between an update operation which fully replaces a resource (including data loss) from those updates which cause some other kind of downtime (e.g a server or database reboot).
The documentation maps both of these concepts to 'Update requires: some interruption' and the resource spec maps only the fully immutable replacement operation, as does the schema currently.
We could include a schema property to signal that a property may cause downtime without data loss as a distinguishing concept.
The text was updated successfully, but these errors were encountered: