This message was deleted.

sparse-intern-71089

05/07/2021, 12:08 PM

This message was deleted.

quiet-architect-74241

05/07/2021, 12:59 PM

What error are you getting? Did you add the PULUMI_ACCESS_TOKEN as an environment variable to you Azure CLI task? This works for me:

Copy code

- bash: |
    pulumi stack select $(stack) --cwd $(pulumiFolder)
    pulumi stack output -j --cwd $(pulumiFolder)
  env: 
    PULUMI_ACCESS_TOKEN: $(pulumi.access.token)

some-flower-64874

05/07/2021, 1:10 PM

There is no pulumi access token as I'm using an azure blob container for the back end. If I had an access token the problem wouldn't exist because there'd be no confusion between the SP settings for running the script and settings for the connection to the container.

some-flower-64874

05/07/2021, 1:11 PM

However I do have an answer - I can do a pulumi stack export to a file and since the export contains the outputs for the stack I can pull those out of the json without much effort (powershell is a wonderful thing at times) I'm potentially sorted

some-flower-64874

05/07/2021, 1:12 PM

pulumi stack output still needs a --file option though

👍 1

4 Views

Open in Slack

Previous Next

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.