-
Notifications
You must be signed in to change notification settings - Fork 1
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
upgrade-provider GitHub Actions workflow #19
Conversation
…am TF provider simultaneously
…name' are required according to the pulumi-upgrade-provider action.yml code) https://github.com/pulumi/pulumi-upgrade-provider-action/blob/main/action.yml\#L8-L14
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dustin-ruetz workflow is ok. However, I did encounter myself that your Github repo needs the issue/PR labels set which are listed in this issue:
For this workflow not to fail, make sure you add these to this repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a good pipeline to me based on the resources you've mentioned.
I've left 2 questions that don't block the PR from moving forward.
cron
schedule (note that this schedule may be modified in future commits), and if successful it should produce an auto-upgrade PR for this pulumi-onepassword bridge provider if it finds upstream changes from the terraform-provider-onepassword repo.