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
{{ message }}
This repository has been archived by the owner on May 16, 2024. It is now read-only.
When trying to deploy 2x deployments using different stackName with the regular prod deployment (using gdeploy, not mage dev:deploy) there is a name collision on some resources:
Final stack status: ROLLBACK_COMPLETE
Messages:
- APIDBTableA8FD77F9: Granted already exists in stack arn:aws:cloudformation:us-west-2:975713946117:stack/CommonFate/cbacbfc0-400e-11ee-8249-0aefbb48e0c7
- EventBusE9ABF535: Resource handler returned message: "Event bus Granted already exists." (RequestToken: 5f13e7af-0f7a-96dd-3ee3-5d10959d1040, HandlerErrorCode: AlreadyExists)
[!] Your Common Fate deployment update ended in status ROLLBACK_COMPLETE
The text was updated successfully, but these errors were encountered:
Similarly, glide wizards put the secrets with a specific prefix apiToken: awsssm:///granted/providers/okta/apiToken:1 rather than using, maybe, the stackName
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When trying to deploy 2x deployments using different
stackName
with the regular prod deployment (usinggdeploy
, notmage dev:deploy
) there is a name collision on some resources:The text was updated successfully, but these errors were encountered: