Hi all! I started using the pulumi github action for PRs (with PR Comments) https://www.pulumi.com/docs/guides/continuous-delivery/github-actions/#comments-by-github-actions The bot instead of commenting the short description like in the picture (I guess is a

pulumi preview --supress-outputs

) adds the all output. The step is pretty similar to the example

- uses: pulumi/actions@v3
        with:
          command: preview
          stack-name: dev
          comment-on-pr: true
          github-token: ${{ env.GITHUB_TOKEN }}
          work-dir: ${{ env.working-directory }}
        env:
          PULUMI_ACCESS_TOKEN: ${{ env.PULUMI_ACCESS_TOKEN }}

Can someone help me with this?

@victorious-megabyte-32350 I have this repo where I play with pulumi and github actions. https://github.com/MitchellGerdisch/github-actions-play I have a workflow for PRs that does the short descriptions as described in the docs. You can see the workflow and the PR with the comment. I hope this helps.

@witty-candle-66007 I'll check on that right now. Regarding the

env.GITHUB_TOKEN

is because in the job I added environment values Let me share that part of the code:

jobs:
  InfrastructurePreview:
    name: Pulumi Preview
    runs-on: ubuntu-latest    
    env:
      working-directory: ./infrastructure
      AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
      AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
      PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    steps:
      - uses: actions/checkout@v2        
      - name: Use Node.js
        uses: actions/setup-node@v2
        with:
          node-version: '14.x'
      - name: Configure AWS Credentials
        uses: aws-actions/configure-aws-credentials@v1
        with:
          aws-access-key-id: ${{ env.AWS_ACCESS_KEY_ID }}
          aws-region: us-west-2
          aws-secret-access-key: ${{ env.AWS_SECRET_ACCESS_KEY }}
      - name: Install Dependencies        
        run: yarn install --frozen-lockfile        
        working-directory: ${{ env.working-directory }}
      - uses: pulumi/actions@v3
        with:
          command: preview
          stack-name: dev
          comment-on-pr: true
          github-token: ${{ env.GITHUB_TOKEN }}
          work-dir: ${{ env.working-directory }}
        env:
          PULUMI_ACCESS_TOKEN: ${{ env.PULUMI_ACCESS_TOKEN }}

I see. It’s a non-issue (the env.GITHUB_TOKEN thing) then.

Is there something that I need to configure on github or pulumi ? I mean, I'm getting something like this:

🍹 Previewing update (company/dev)

View Live: <https://app.pulumi.com/company/infrastructure/dev/previews/4e68223d-5963-2bd8-5200-4427721b078c>


pulumi:pulumi:Stack infrastructure-dev running 
+  aws:s3:Bucket test-bucket-pr-ci create 
aws:dynamodb:Table Table1
aws:dynamodb:Table Table2
aws:s3:Bucket web-app-dev  
-  aws:s3:Bucket another-bucket delete 
pulumi:pulumi:Stack infrastructure-dev  

Outputs:
~ webApp   : {
    ...values
}
~ dynamodbTables   : {   
    ..tables
}
...rest

Resources:
+ 1 to create
~ 1 to update
- 17 to delete
19 changes. 82 unchanged

Right, that run was from a stack that had no resources. So I reran a test sequence as follows: • Started with an empty stack. • Project now only creates a resource group (Azure) and outputs the resource group ID • Caused PR preview change: The PR comment showed the creation list but no output. • Ran pulumi up event to get the stack created. • Update code to also create a storage account and output a storage account ID. • This caused a PR preview which showed the new SA resource and the new output promise. It’s interesting to note that the existing resource group ID output is not included in the PR comment. But it looks like this method will show outputs

Sorry Mitch, I had some meetings. Now I'm free. I've looked all the commits and the PR. I guess (correct me if I'm wrong) If you don't export the resource (rgId) it won't show the output section. (like in the pulumi documentation)

Outputs are an expected part of the PR comment. I need to dig into why I don’t see both of my outputs in my PR comment, though. In other words, it appears to be inconsistent on my end and so may be a bug in that it is missing an output.

Awesome, Thank so much Mitch with the help.

I am curious if you are seeing all outputs and their values in the PR comment or only outputs that are created or updated due to the changes that the preview has identified