Komal
Komal
Hey folks! #8058 is now closed and will be included in the next release (next week). Take a look at the [accompanying PR description](https://github.com/pulumi/pulumi/pull/8071#issue-743792213) for details on the added option...
I believe this is fixed in the latest release. Please reopen if this is not the case
Currently, it is possible to do this by adding the action in "install only" [mode](https://github.com/pulumi/actions#installation-only) and then running the `pulumi package publish` command in a subsequent step. This issue tracks...
@hcharley this issue specifically targets replicating the functionality of CLI commands such as `pulumi state rm`, `pulumi state unprotect`, etc. But you are correct in that all of the same...
Hmm no luck, that reasonably errors with: `Error: yaml: line 2: did not find expected key`
> I'd love to know what the YAML that triggers this looks like... Yeah, I agree. It would be nice if we had the request payload for Check calls. Either...
Yeah I realized after I dug into it further. I think it would be helpful to give a better error so that's clear to the user.
>RST parameter doc notation is not currently recognized by either IDEs In my experience, this is the format recognized by JetBrains products, but not by VSCode (prefers google style docstrings)....
>I'm not sure about including both places - the Sphinx comment scared me that that'd duplicate something in the docs As @justinvp mentioned, we don't use sphinx to generate documentation...
Yeah that's fair. Would love to see what sort of effect the bloat has on size/speed 🙏🏽