@echoing-dinner-19531 and guys. the video is very interesting but we’re using a bit different with github action. the current configuration is

- name: Pulumi up on ${{ matrix.stack }}
        id: pulumi_up
        uses: pulumi/actions@v4.5.0 # bug with action@v4 <https://pulumi-community.slack.com/archives/C84L4E3N1/p1675078507601099>
        with:
          command: up
          stack-name: ${{ matrix.stack }}
          comment-on-pr: true
          github-token: ${{ secrets.GITHUB_TOKEN }}

so with 1password integrated, is there is way to add op value into this action rather than using custom step pulumi up (like in video). I’m thinking about • using

op inject

command to generate .env file then export it before step

pulumi_up

• or

pulumi/actions

support run custom command to help

op

able run within the same step. Could you help me check and share me some suggestion?

I don't think the actions written in a way to support this directly, but it's a reasonable thing to raise an issue about. Probably just needs a way to set the

op run --env-file .env --

command prefix somehow.

is possible if I write two more step, 1.

op inject -i .env -o .<http://env.ci|env.ci>

2. then use action https://github.com/marketplace/actions/load-env-file then last step pulumi/action

That seems reasonable as well