Praneet Loke

@douglasg14b > but turns out this action does not respect the working-directory default I am not sure if there is a job-level default for working directory in GH actions though?...

Yeah it's only for the `run` step. It's not for _all_ steps to use.

@pierskarsenbarg > This means that if you have an iternal policy that means you need to not use auto-naming, you're not going to be able to delete keyvaults because we...

@pierskarsenbarg thank you for the explanation! :)

@UnoSD thank you for submitting the issue. I have a few clarifying questions if you could answer them please? > I cannot use the task as I cannot set the...

@UnoSD the task has an input param called `args`. You should be able to pass `--secrets-provider="azurekeyvault://$KEYVAULT/keys/pulumi"` to it, as well as any other flag that the command accepts. For example,...

This should be possible using the DevOps REST API to create comment threads in PRs. There's a Node.js client [SDK](https://github.com/Microsoft/azure-devops-node-api) for interacting with the API. Additional refs https://docs.microsoft.com/en-us/rest/api/azure/devops/git/pull-request-threads/create?view=azure-devops-rest-6.0&tabs=HTTP https://docs.microsoft.com/en-us/rest/api/azure/devops/git/pull-request-thread-comments/create?view=azure-devops-rest-6.0&tabs=HTTP

> This would be very helpful especially since the Pulumi GitHub App is not working! @dblair-cet what's not working specifically in the GH App?

@darnmason `pulumi` not installing the plugins automatically when you use the `binary` option is expected since the Pulumi CLI doesn't support it when you use the `binary` option. Another related...

@darnmason since v1.0.9 you should be able to use the task extension to simply install the CLI and then run a single `script` task to install all plugins. It's still...