Allow for internal crane pulls and pushes without a tunnel + explicit auth#1851
Merged
Racer159 merged 3 commits intozarf-dev:mainfrom Jun 28, 2023
Conversation
dgershman
requested review from
Madeline-UX,
Noxsios,
Racer159,
YrrepNoj and
jeff-mccoy
as code owners
✅ Deploy Preview for zarf-docs canceled.
|
dgershman
changed the title
YrrepNoj
approved these changes
Jun 28, 2023
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
3 participants
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.
Allow for internal crane pulls and pushes without a tunnel + explicit credentials
Description
This gives the same ability as #1835 to
zarf tools crane pushandzarf tools crane pull. Essentially, you shouldn't have to create a tunnel and auth to the registry to pull or push images to it.Related Issue
#1835
Type of change
Checklist before merging