add support for oci push#234
Open
monotek wants to merge 1 commit into
Open
Conversation
Signed-off-by: André Bauer <monotek23@gmail.com>
This file contains hidden or 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
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.
Add OCI registry push support via cr push
Adds three new inputs that let the action push packaged charts to an OCI registry, alongside (or instead of) the existing GitHub Pages flow:
oci_registry_url— when set, triggers an OCI push (e.g.oci://ghcr.io/myorg/charts)oci_username— optional, falls back to the local registry credential storeoci_password— optional, falls back to the local registry credential storeUnder the hood, this wires a new
push_charts()function incr.shthat invokescr pushaftercr upload(in both the packaging andskip_packagingcode paths). The existingskip_existinginput is reused forcr push --skip-existing.README adds the inputs to the reference table and ships a worked example showing the recommended auth flow via
docker/login-actionbefore the action runs (so credentials land in~/.docker/config.jsonandcr pushpicks them up automatically).This PR cannot be merged until helm/chart-releaser#622 is merged and released as a tagged version of
chart-releaser. The newcr pushcommand does not exist in any released version yet — using this action with the defaultversion: v1.7.0will fail withunknown command "push".After #622 ships, the default
versioninaction.ymlshould be bumped to the release that containscr pushas a follow-up.