Hey all, Anyone have experience with the

remove

option from the Pulumi GitHub action? When my action runs, it shows a warning that

remove

isn't recognised, continues and does not delete the stack from Pulumi after successfully destroying the resources:

Warning: Unexpected input(s) 'remove', valid inputs are ['command', 'stack-name', 'work-dir', 'comment-on-pr', 'comment-on-pr-number', 'github-token', 'cloud-url', 'secrets-provider', 'parallel', 'message', 'config-map', 'expect-no-changes', 'diff', 'replace', 'target', 'target-dependents', 'policyPacks', 'policyPackConfigs', 'refresh', 'upsert', 'edit-pr-comment', 'pulumi-version', 'color']

...

  Resources:
      - 35 deleted
  
  Duration: 4m7s
  
  
  The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained. 
  If you want to remove the stack completely, run `pulumi stack rm company/infra`.

I'm using

@v3

on the action and I can see the

remove

option in the docs:

- uses: pulumi/actions@v3
  with:
    command: destroy
    stack-name: company/${{ inputs.environment_name }}
    work-dir: ${{ env.working_directory }}
    upsert: false
    remove: true

This feature is pending for the next release. See: https://github.com/pulumi/actions/blob/master/CHANGELOG.md

Ah, I just spotted this too. Thanks for pointing out! I've just specified the commit sha as shown in GitHub actions to test. Although I get no warning at the top using it, the stack still isn't deleted:

Run pulumi/actions@a8f22a75ed2d159b2b05326e3cba79b1fcdaab18
  with:
    command: destroy
    stack-name: company/infra
    work-dir: iac/pulumi
    upsert: false
    remove: true

...

  Resources:
      - 35 deleted
  
  Duration: 4m42s
  
  
  The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained. 
  If you want to remove the stack completely, run `pulumi stack rm company/infra`.