-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oras push/cp --digest-only #326
Milestone
Comments
@SteveLasker - Looks like you moved this back to the wrong repo. This is a CLI experience feature request and not a library issue. Please close this or transfer it to the CLI repo. |
|
@shizhMSFT, correct. |
@JunczhuMSFT this is related to the |
Closed by notaryproject/notation#432 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To support tag update scenarios, where a new digest, and all its references should be pushed before a tag update is applied, we need a way to push a container image, or any
artifactType
, deferring the tag application.Initially, I considered
docker push --digest-only
, and that may still be the best idea. Except, that would require a change to the docker client.This proposal focuses on
oras push
with a--digest-only
flag.Perhaps
oras cp
with--digest-only
See Docs: Add Promoting Scenario oras-project/oras#98 for more info
The text was updated successfully, but these errors were encountered: