-
Notifications
You must be signed in to change notification settings - Fork 73
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
Support the --exclude-protected
on destroy
#628
Comments
Hi @garethbudden , thanks for opening this issue. What do you think @cobraz? |
@RobbieMcKinstry I don't miss this flag specifically, but I agree that either We now have to resort to installing Pulumi CLI. |
Hm, yeah... I wonder about adding |
That's definitely a decent option! But, having read through the action-code in an effort to make a PR; I still don't see how you feed that into pulumi-automation. From what I gather, only very specific fields are taken into account there. Perhaps it just requires a PR to that module as well :) |
Sorry to talk across you on two threads, Commander! I'm going to link this related conversation here just for posterity, in which we discuss a possible approach to side-step automation API. |
This functionality in the GHA would be great |
Hello!
Issue details
For similar reasons outlined in the issue that resulted in the
--exclude-protected
being added to the CLI, it would be good to be able to provide this flag in the GitHub Action.The text was updated successfully, but these errors were encountered: