Closed sebdah closed 10 years ago
An alternative approach would be to skip the project annotation and instead only include the environment and the stack in the stack name (environment-stack
). In the above case each project would have to name their environment to e.g. ProjectA-prod
. That would in turn guarantee a unique stack name.
If you have a setup where many projects reside within the same AWS account, you will need something more to distinguish the various environment. For example you might have
ProjectA
andProjectB
. Both of those projects want to have an environment calledstage
and one calledprod
. Those environments all have a stack calledwebserver
.There will be a collision in the stack name, as we will currently set it to
webserver
. I would like us to set it toProjectA-stage-webserver
.