Currently WorkGroupConfiguration is used for create operations, and WorkGroupConfigurationUpdates is used for update stack operations. This is really confusing for customers and does not follow how you would expect a CFN resource to behave.
Planned fix: Release an update such that WorkGroupConfiguration can be used in both create and update operations, and deprecate WorkGroupConfigurationUpdates. Ideally do so in a way that won't break existing templates.
I will keep this issue open as a way to track progress on this update.
Currently
WorkGroupConfiguration
is used for create operations, andWorkGroupConfigurationUpdates
is used for update stack operations. This is really confusing for customers and does not follow how you would expect a CFN resource to behave.Planned fix: Release an update such that
WorkGroupConfiguration
can be used in both create and update operations, and deprecateWorkGroupConfigurationUpdates
. Ideally do so in a way that won't break existing templates.I will keep this issue open as a way to track progress on this update.