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.

Sign up for GitHub

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

Jump to bottom

Consider setting up this repository to test if upgrade workflows succeed #500

Open

guineveresaenger opened this issue Nov 4, 2024 · 1 comment

Labels

kind/engineering

Contributor

guineveresaenger commented Nov 4, 2024

It would be great if upgrade-provider Workflows such as this one could be tested in this repository.

pulumi-bot added the needs-triage label

guineveresaenger mentioned this issue

Do not check for upgrade #499

Merged

guineveresaenger removed the needs-triage label

Member

danielrbradley commented Nov 8, 2024

I've made some progress towards this:

Created 2 releases of the upstream TF provider (v0.0.1 and v0.0.2).
Upgraded this provider to v0.0.1 as an initial baseline version
Re-enabled the upgrade-provider workflow in this repo
Added an optional input for the ref of the version of upgrade-provider to use in the workflow so we can test pre-release versions

Next step: Design an automated process from ci-mgmt to:

Cut a new version of the upstream tf provider.
Trigger the upgrade workflow on the branch of the PR.
Assert that:
- The upgrade issue is created.
- The upgreade PR is created.
- The PR will close the issue.
- The PR build passes.
Close the PR and issue (add resolution & assignee).

mikhailshilkov added the kind/engineering label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment