Skip to content
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

Open
Marius-O opened this issue Apr 26, 2022 · 4 comments · May be fixed by #1046
Open

Add a verbosity flag to the pulumi/actions #589

Marius-O opened this issue Apr 26, 2022 · 4 comments · May be fixed by #1046
Labels
area/cicd kind/enhancement Improvements or new features

Comments

@Marius-O
Copy link

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
Copy link
Contributor

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
Copy link

@RobbieMcKinstry is args a planned feature with a timeline?

@RobbieMcKinstry
Copy link
Contributor

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
Copy link
Member

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

@ekbduffy ekbduffy linked a pull request Dec 10, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cicd kind/enhancement Improvements or new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants