Add a verbosity flag to the pulumi/actions

[Marius-O]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I was recently debugging an issue where a lock was not being released upon deployment completion which was related to the SAS token that did not have delete permissions. It's impossible to debug when using the github actions so had to migrate to using a script so I can make use of the --verbose flag.

Affected area/feature

pulumi/actions

[RobbieMcKinstry]

Hey @Marius-O thanks for opening this issue. I think you're right; if we support the flag in the CLI, it makes sense to support it in the action as well. However, I think this issue suffers from the same problem as #628 -- I think it would be better to provide an args input as an escape hatch for all arguments. That would let us pass options to subcommands as well.

So I think there are two routes we could go here: either add support for the verbosity flag directly or add support for the escape hatch. I believe we would accept a PR for either.

[o-alexandrov]

@RobbieMcKinstry is args a planned feature with a timeline?

[RobbieMcKinstry]

Hi @o-alexandrov I'm sorry, I'm no longer an OSS maintainer at Pulumi, so I'm unable to answer that question. I've offboarded my maintenance responsibilities to @justinvp.

[justinvp]

@o-alexandrov, it's not currently planned.

[thnk2wn]

This would be nice otherwise the action can't be used in many cases. Is there a way to set pulumi verbosity via environment variable?