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.

Pulumi Community

probably you have to type only stack name like `pulumi stack select production`

```/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 &gt; pulumi.json```
I do do that ad seems to be propagating correctly as in the error is trying to access
```dfds-frontend/production```

what’s the output of `pulumi stack ls`  ?

is it because of
```<https://app.pulumi.com/dfds-frontend/dotcom-gatsby/production>```
should i do?
```/home/ubuntu/.pulumi/bin/pulumi stack select dfds-frontend/dotcom-gatsby/$RELEASE_ENVIRONMENTNAME```

output is just
```2020-05-22T08:25:30.1958466Z NAME  LAST UPDATE  RESOURCE COUNT  URL```

created stack yaml file manually, not by pulumi cli?

may need to init stack with `pulumi stack init stack_name`

okay interesting everything used to work last week, but our acc got cancelled and I just have added payment for that

```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