Fraser Waters

That looks like https://github.com/pulumi/actions/issues/1010.

Would it be possible to run a "pulumi stack select" first and if that fails ignore and skip the destroy? Or (maybe in conjunction with the above) we make the...

🤦‍♂️ I didn't even notice what repo I was in. Yes something like this sounds reasonable. I think the only question is if this flag should only apply to destroy...

I think the "pulumi-version" option is just a string so we could just allow "latest" or a semver range there (continuing to default to "^3" when unset)

This seems a reasonable request. I'm a little hesitant about the action just becoming a shim over everything the CLI does, and this is another small tick towards that, but...

This was actually released in [v5.1.0](https://github.com/pulumi/actions/releases/tag/v5.1.0)

Sounds like this should re-open to track that it's not yet usable.

> Preferably I'd like this to be done within the automation API itself, using the installPlugin method but that does not take a server argument (I'd also like to not...

> Additionally, it'd be nice if there was an escape hatch in the form of a config variable specifying the path to a CLI binary that has already been provided...

> Do we just not pass and hydrate the configuration within the dynamic provider process? That wouldn’t seem terribly difficult to do unless I’m missing something? Dynamic providers are an...