-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a verbosity flag to the pulumi/actions #589
Comments
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 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. |
@RobbieMcKinstry is |
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. |
@o-alexandrov, it's not currently planned. |
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? |
Hello!
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
The text was updated successfully, but these errors were encountered: