Add "branch_name", "version" and "regorg" parameters to the "Provider Publish Service Artifacts" reusable workflow #156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ulucinar
force-pushed
the
parameterize-regorg
branch
2 times, most recently
from
f23acdf to
35b706c
Compare
"Provider Publish Service Artifacts" reusable workflow Signed-off-by: Alper Rifat Ulucinar <[email protected]>
ulucinar
force-pushed
the
parameterize-regorg
branch
from
35b706c to
8f1bf4f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR parameterizes the image registry and repo, the branch name and the version used for building and publishing the provider packages so that we can still use the reusable workflow
Provider Publish Service Artifactsfor publishing packages to repositories other thanxpkg.upbound.io/upboundand with customizable version strings.I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
Tested manually under a different Github org.