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

Do not run upgrade check for this provider #202

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

guineveresaenger
Copy link
Contributor

Because the upstream provider is pre-stable release, we run upgrades manually.

Fixes #200.

@guineveresaenger guineveresaenger requested a review from a team November 5, 2024 21:22
Copy link

github-actions bot commented Nov 5, 2024

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

Maintainer note: consult the runbook for dealing with any breaking changes.

Copy link
Member

@mjeffryes mjeffryes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine to do this as a quick workaround, but I wonder if we couldn't make the upgrade job resilient to this case?

Makefile Outdated
@@ -180,7 +180,6 @@ bin/pulumi-java-gen: .pulumi-java-gen.version
# - Run make ci-mgmt to apply the change locally.
#
ci-mgmt: .ci-mgmt.yaml
find .github/workflows/*.yml -type f ! -name "$(PACK)*.yml" -delete
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm surprised that this changes with the checkUpstreamUpgrade flag change

Copy link
Member

@iwahbe iwahbe Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an unrelated change from bumping ci-mgmt to latest. Since ci-mgmt isn't versioned, each time a change is made to .ci-mgmt.yaml and then applied with make ci-mgmt the latest version of ci-mgmt is pulled.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was a recent change in ci-mgmt that had not done the nightly percolation. It's a legitimate change; I verified.

@guineveresaenger guineveresaenger force-pushed the guin/skip-upstream-upgrade branch from 7509f22 to 3e012ee Compare November 6, 2024 17:17
@guineveresaenger guineveresaenger enabled auto-merge (squash) November 6, 2024 17:18
@guineveresaenger guineveresaenger added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label Nov 7, 2024
@mikhailshilkov mikhailshilkov added impact/no-changelog-required This issue doesn't require a CHANGELOG update and removed impact/no-changelog-required This issue doesn't require a CHANGELOG update labels Nov 7, 2024
@guineveresaenger guineveresaenger merged commit 0809479 into main Nov 7, 2024
23 checks passed
@guineveresaenger guineveresaenger deleted the guin/skip-upstream-upgrade branch November 7, 2024 08:41
@pulumi-bot
Copy link
Contributor

This PR has been shipped in release v0.3.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Workflow failure: Upgrade provider
5 participants