-
Notifications
You must be signed in to change notification settings - Fork 277
Feature/docker validate sha #2971
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
Conversation
facc5d9 to
6dcad6b
Compare
6dcad6b to
107f393
Compare
c8fc46d to
eeaa95c
Compare
eeaa95c to
f580e09
Compare
f580e09 to
de14255
Compare
de14255 to
1409f88
Compare
docs/buildtools/dockerpush/help.go
Outdated
| The docker push args to run docker push.` | ||
| The docker push args to run docker push. | ||
| --validate-sha |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since it is a flag, do we need to update here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, you are right, for flags we don't need to update here.
| Usage: "[Default: false] Set to true if you'd like to use the native client configurations. Note: This flag would invoke native client behind the scenes, has performance implications and does not support deployment view and detailed summary` `", | ||
|
|
||
| }, | ||
| validateSha: cli.BoolFlag{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what ist he difference between container push command and docker, dockerPush is it like OCI support?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I understood was
- DockerPush Specifically for Docker images, using the Docker CLI under the hood
- ContainerPush - A more generic command that supports multiple container technologies, not just Docker.
Since both commands perform pushing operations that could benefit from SHA validation, it makes sense to add the flag to both.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I understood was
- DockerPush Specifically for Docker images, using the Docker CLI under the hood
- ContainerPush - A more generic command that supports multiple container technologies, not just Docker.
Since both commands perform pushing operations that could benefit from SHA validation, it makes sense to add the flag to both.
| ContainerPush: { | ||
| BuildName, BuildNumber, module, url, user, password, accessToken, sshPassphrase, sshKeyPath, | ||
| serverId, skipLogin, threads, Project, detailedSummary, | ||
| serverId, skipLogin, threads, Project, detailedSummary, validateSha, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the flag required here as well as in jfrog-cli-artifactory?
56eb6ae to
f8364d2
Compare
a73b7f1 to
2ec4dda
Compare
2ec4dda to
542ac45
Compare
542ac45 to
559cdc9
Compare
devbranch.go vet ./....go fmt ./....Add
--validate-shaflag for Docker push commandDescription
This PR adds a new
--validate-shaflag to the Docker push command. When enabled, the flag allows the CLI to use the image's SHA digest for validation instead of the tag name during Docker push operations. This is particularly useful when pushing to virtual repositories where the tag might exist with different content in higher priority repositories.Changes
Testing
jf rt docker-push) and new (jf docker push) CLI syntaxRelated PRs