This message was deleted.

sparse-intern-71089

02/23/2023, 4:31 PM

This message was deleted.

melodic-tomato-39005

02/23/2023, 4:42 PM

I think here is fine.

jolly-fall-57688

02/23/2023, 4:49 PM

We would like to incorporate the Pulumi Actions into our CI/CD workflow. I looked through the examples but could not find a way set a variable for our "stack-name". We would like to use GitHub Environments to help trigger deployments with Pulumi. Right now the only way I can get our action to work is by hardcoding a stack-name.

Copy code

- uses: pulumi/actions@v4
        with:
          work-dir: fargate/infra
          command: preview
          stack-name: acmecorp/mystack/dev

jolly-fall-57688

02/23/2023, 4:50 PM

We would like to have stage and prod deployments use GitHub Actions.

melodic-tomato-39005

02/23/2023, 4:55 PM

You can use a regular Github Actions variable to make the stack name dynamic. There’s no special Pulumi support required. It would look something like this:

Copy code

stack-name: ${{ env.stack }}

jolly-fall-57688

02/23/2023, 4:55 PM

Thank you.

👍 1

strong-match-67698

02/24/2023, 7:48 AM

or use inputs, those are basic mechanisms of github actions

3 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.