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
We renamed landsat/cloudformation.yml to cloudformation.yml as part of #41 because it had already been deployed as the its-live-monitoring-prod and its-live-monitoring-test CloudFormation stacks. Ideally we want the Landsat stack to be a sub-stack under the top-level CF template, but we didn't want to deal with renaming resources as part of that PR. I'm not sure how much of a hassle it will be to re-deploy those resources under a new sub-stack.
The text was updated successfully, but these errors were encountered:
We renamed
landsat/cloudformation.yml
tocloudformation.yml
as part of #41 because it had already been deployed as theits-live-monitoring-prod
andits-live-monitoring-test
CloudFormation stacks. Ideally we want the Landsat stack to be a sub-stack under the top-level CF template, but we didn't want to deal with renaming resources as part of that PR. I'm not sure how much of a hassle it will be to re-deploy those resources under a new sub-stack.The text was updated successfully, but these errors were encountered: