Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conditional support for replace1/replace2 templates #1940

Open
roleyfoley opened this issue Feb 21, 2022 · 0 comments
Open

Conditional support for replace1/replace2 templates #1940

roleyfoley opened this issue Feb 21, 2022 · 0 comments

Comments

@roleyfoley
Copy link
Contributor

Expected Behaviour

When developing components it is possible to specify which resources trigger the use of the replace templates if they have been flagged for replacement

Current Behaviour

If any resource is marked for replacement template is run, this can create unexpected changes to the more complex resources which require replace handling. I.e. alarms being replaced as part of a DB instance.

Possible Solution

This really requires more complex definition of deployments and would require the engine to generate a contract outlining how to run the deployment as the engine handles defining and managing resources.

Context

this would make replace template usage safer and more easily understood

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant