Unexpected error encountered: HttpError: Not Found when using "delete-env"

[jessebye]

I am getting an error Unexpected error encountered: HttpError: Not Found during the delete-env step.

Here's the full logs:

Run bobheadxi/deployments@v1.1.0
  with:
    step: delete-env
    token: ***
    desc: Environment was pruned
    env: pulumi-service-pr-51
    debug: true
    auto_inactive: false
targeting <redacted>/pulumi-service
'delete-env' arguments {
  coreArgs: {
    environment: 'pulumi-service-pr-51',
    description: 'Environment was pruned',
    logsURL: 'https://github.com/<redacted>/pulumi-service/commit/0f30981[2](https://github.com/<redacted>/pulumi-service/runs/5382231462?check_suite_focus=true#step:6:2)984b6eacbe7ee8f89ce5d9da2[3](https://github.com/<redacted>/pulumi-service/runs/5382231462?check_suite_focus=true#step:6:3)0a3b30/checks'
  }
}
unexpected error encountered: HttpError: Not Found
Error: unexpected error encountered: HttpError: Not Found - see logs for more information

Not sure why this is happening? I can confirm that a deployment matching that environment does exist for this repo.

[bobheadxi]

This seems to be a permissions issue - see: #85

[jessebye]

@bobheadxi strange. I can use an alternate GitHub action to inactivate/delete the deployments and environment fine:

    - name: Clean up deployments
      uses: strumwolf/delete-deployment-environment@v2
      with:
        token: ${{ secrets.GITHUB_TOKEN }}
        environment: ${{ github.event.client_payload.environment }}

This is the same GITHUB_TOKEN I was using for your action. Do you still think it's permissions-related?

[bobheadxi]

Interesting, thanks - I will take a closer look!

[bradsbrown]

It's possible the issue here is that you can't delete an active environment -- you must first set it inactive and then delete it, according to the Github Docs.

If the repository only has one deployment, you can delete the deployment regardless of its status. If the repository has more than one deployment, you can only delete inactive deployments.

So either delete-env should inactivate-then-delete, or we as users should have those two steps stacked back-to-back in our workflow, right?

[asychev]

Tried combination of deactivate-env and then delete-env - does not work

[asychev]

Same issue for me, strumwolf/delete-deployment-environment works, this action does not

[bobheadxi]

Hey everyone, unfortunately, I haven't been able to take a look at this and probably won't have the bandwidth to actively maintain this project for the time being. If someone finds a good way forward I would appreciate a PR! I just cut https://github.com/bobheadxi/deployments/releases/tag/v1.2.0 which includes a recent contribution which changes up how delete-env works a bit, though not in a way that resolves the issue here I think: #101

[bobheadxi]

If anyone is open to helping me maintain this project I'd be super grateful and happy to chat, please reach out to me via twitter, email, or #103! 🙏