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
I've raised this in Discord, but raising here as well incase any else has the same problem and can help.
We are running into a strange issue with autodeploy. We have 4 environments, mapped to 3 AWS accounts (pr's and dev go to dev account) When we merge into production, the deploy runs, but it deploys into the dev account. I think my SST config is correct as i can see sst deploy --stage prd running in the logs when i merge into prod branch.
In the screenshot, you can see the 4 environments, but prd deploy does not deploy to expected account. I'm sure i'm missing something obvious here, how can i debug it?
You can see below the merge into production triggers sst deploy --stage prd
I'm sure i'm doing something wrong, but i'm not sure how to debug this further, does anyone have idea what could be going wrong or steps i can follow to find out whats happening?
Thanks!
The text was updated successfully, but these errors were encountered:
I've raised this in Discord, but raising here as well incase any else has the same problem and can help.
We are running into a strange issue with autodeploy. We have 4 environments, mapped to 3 AWS accounts (pr's and dev go to dev account) When we merge into production, the deploy runs, but it deploys into the dev account. I think my SST config is correct as i can see
sst deploy --stage prd
running in the logs when i merge into prod branch.In the screenshot, you can see the 4 environments, but prd deploy does not deploy to expected account. I'm sure i'm missing something obvious here, how can i debug it?
You can see below the merge into production triggers
sst deploy --stage prd
I'm sure i'm doing something wrong, but i'm not sure how to debug this further, does anyone have idea what could be going wrong or steps i can follow to find out whats happening?
Thanks!
The text was updated successfully, but these errors were encountered: