Export registry generateToken function #2176
Draft
Conversation
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
git-basejump
bot
force-pushed
the
joshbwlng/registry-token-fn
branch
from
7feb4d3 to
0880b8b
Compare
Change-type: minor
git-basejump
bot
force-pushed
the
joshbwlng/registry-token-fn
branch
from
0880b8b to
51a667c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Change-type: minor
See: https://balena.fibery.io/Work/Project/Experimental-build-for-moving-to-a-new-registry-2144
Export the
generateToken()function so we can call that internally to generate registry tokens as needed, primarily for listing repositories and marking images for deletion.