Fix the repo name calculation logic in the Updoc CI workflow #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
As we moved the official providers
upbound/provider-{aws, azure, azuread, gcp}
to their homescrossplane-contrib/provider-upjet-{aws, azure, azuread, gcp}
, we will need to fix/change the provider repo name calculation in the reusableUpdoc
workflow so that we still compute the old repo names for these providers. This is required because although we have moved these providers to new repositories, the published package names are kept intact for backwards compatibility reasons.I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Tested the changes proposed in this PR here: https://github.com/ulucinar/uptest/actions/runs/8283714517/job/22667549446
Please note that even if we pass
provider-aws
orprovider-upjet-aws
, the calculated package names are as expected, e.g.,provider-aws-ec2
.