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

Auto-merge bridged provider upstream upgrades where tests pass #1344

Closed
75 tasks
VenelinMartinov opened this issue Feb 3, 2025 · 0 comments · Fixed by #1378
Closed
75 tasks

Auto-merge bridged provider upstream upgrades where tests pass #1344

VenelinMartinov opened this issue Feb 3, 2025 · 0 comments · Fixed by #1378
Assignees
Labels
kind/engineering Work that is not visible to an external user resolution/fixed This issue was fixed

Comments

@VenelinMartinov VenelinMartinov self-assigned this Feb 3, 2025
@pulumi-bot pulumi-bot added the needs-triage Needs attention from the triage team label Feb 3, 2025
@VenelinMartinov VenelinMartinov added kind/engineering Work that is not visible to an external user and removed needs-triage Needs attention from the triage team labels Feb 3, 2025
VenelinMartinov added a commit to pulumi/pulumi-upgrade-provider-action that referenced this issue Feb 3, 2025
Add a `target-version` arg for upstream provider upgrades.

Related to pulumi/ci-mgmt#1344
github-merge-queue bot pushed a commit that referenced this issue Feb 4, 2025
This PR adds a config `autoMergeProviderUpgrades` which will mark
upstream provider upgrades to be auto-merged. I've also moved the
upgrade-provider call to use the upgrade-provider action like we do with
bridge upgrades.

Related to #1344
VenelinMartinov added a commit to pulumi/pulumi-azuread that referenced this issue Feb 11, 2025
Sets the `AutoMergeProviderUpgrades` ci-mgmt config to false to avoid
auto-merging upstream upgrades. This maintains the current behaviour.

Part of pulumi/ci-mgmt#1344
VenelinMartinov added a commit to pulumi/pulumi-azure that referenced this issue Feb 11, 2025
Sets the `AutoMergeProviderUpgrades` ci-mgmt config to false to avoid
auto-merging upstream upgrades. This maintains the current behaviour.

Part of pulumi/ci-mgmt#1344
VenelinMartinov added a commit to pulumi/pulumi-gcp that referenced this issue Feb 11, 2025
Sets the `AutoMergeProviderUpgrades` ci-mgmt config to false to avoid
auto-merging upstream upgrades. This maintains the current behaviour.

Part of pulumi/ci-mgmt#1344

---------

Co-authored-by: Cory Hall <[email protected]>
VenelinMartinov added a commit to pulumi/pulumi-aws that referenced this issue Feb 11, 2025
Sets the `AutoMergeProviderUpgrades` ci-mgmt config to false to avoid
auto-merging upstream upgrades. This maintains the current behaviour.

Part of pulumi/ci-mgmt#1344
github-merge-queue bot pushed a commit that referenced this issue Feb 11, 2025
This PR changes all Tier2+ providers to auto-merge upstream provider
upgrades. This will save us a lot of clicking.

Fixes #1344

Tier 1 providers are exempt as the config is explicitly false there:
pulumi/pulumi-gcp#2970
pulumi/pulumi-aws#5192
pulumi/pulumi-azure#3002
pulumi/pulumi-azuread#1876
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/engineering Work that is not visible to an external user resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants