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
If you have a launch constraint role defined for a distributed product, you might want to change the role. Based on the observation, this results in an error, as the Puppet tries to associate a new launch constraint not taking into account the existing one.
port-xyz|prod-xyz already exists in stack arn:aws:cloudformation:us-east-1:1234567890:stack/launch-constraints-for-portfolio/86bd5020-56b0-11ed-8102-0a43c1234567
So, if a launch constraint role is defined for a product in the manifest file, Puppet should:
remove the old launch constraint role (CloudFormation stack)
apply the new launch constraint role based on the manifest
If you have a launch constraint role defined for a distributed product, you might want to change the role. Based on the observation, this results in an error, as the Puppet tries to associate a new launch constraint not taking into account the existing one.
port-xyz|prod-xyz already exists in stack arn:aws:cloudformation:us-east-1:1234567890:stack/launch-constraints-for-portfolio/86bd5020-56b0-11ed-8102-0a43c1234567
So, if a launch constraint role is defined for a product in the manifest file, Puppet should:
Example existing manifest:
Example new manifest:
The text was updated successfully, but these errors were encountered: