https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
g
probably you have to type only stack name like 
pulumi stack select production
g
Copy code
/home/ubuntu/.pulumi/bin/pulumi stack select dfds-frontend/$RELEASE_ENVIRONMENTNAME
/home/ubuntu/.pulumi/bin/pulumi refresh
/home/ubuntu/.pulumi/bin/pulumi up
/home/ubuntu/.pulumi/bin/pulumi stack output --json > pulumi.json
I do do that ad seems to be propagating correctly as in the error is trying to access
Copy code
dfds-frontend/production
g
what’s the output of 
pulumi stack ls
?
g
is it because of
Copy code
<https://app.pulumi.com/dfds-frontend/dotcom-gatsby/production>
should i do?
Copy code
/home/ubuntu/.pulumi/bin/pulumi stack select dfds-frontend/dotcom-gatsby/$RELEASE_ENVIRONMENTNAME
sec ill check
output is just
Copy code
2020-05-22T08:25:30.1958466Z NAME  LAST UPDATE  RESOURCE COUNT  URL
🤷‍♂️
g
created stack yaml file manually, not by pulumi cli?
may need to init stack with 
pulumi stack init stack_name
g
okay interesting everything used to work last week, but our acc got cancelled and I just have added payment for that
maybe that was the issue?
locally I do get the proper stack ls
Copy code
NAME                       LAST UPDATE  RESOURCE COUNT  URL
dfds-frontend/dev          1 month ago  28              <https://app.pulumi.com/dfds-frontend/dotcom-gatsby/dev>
dfds-frontend/production*  1 month ago  28              <https://app.pulumi.com/dfds-frontend/dotcom-gatsby/production>
dfds-frontend/staging      1 month ago  28              <https://app.pulumi.com/dfds-frontend/dotcom-gatsby/staging>
if anybody finds this and have the same issue, please check the logged in user of your CI/CD. Issue with us was that we had removed the account that has created the API key. I just logged out and logged in with the correct user and passed the new api key
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by