-
Notifications
You must be signed in to change notification settings - Fork 40
Docker curation supprot #608
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
base: dev
Are you sure you want to change the base?
Conversation
f7e72df to
493aead
Compare
1ca434f to
ff915c5
Compare
e25245f to
a814b8d
Compare
| } | ||
|
|
||
| var ( | ||
| jfrogSubdomainPattern = regexp.MustCompile(`^([a-zA-Z0-9]+)-([a-zA-Z0-9-]+)\.jfrog\.io$`) |
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.
are we sure jfrog images repos always include ".jfrog" ?
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.
As far as ik and worked before, yes.
IF we have Cname, it works the same as selfhosted
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 it means works the same as selfhosted?
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.
the subdomain of on perm customers.
I also found a KB Which explains each one of them and made sure I follwed it
New Command
I added support for running curation checks on Docker images using the following command:
jf ca --image <RT-url>/<repository>/<image>:<tag>Same as docker pull command.
This command allows users to run the curation engine directly on a Docker image stored in Artifactory (or in an upstream remote registry) without pulling the image locally.
How It Works Internally
When the command is executed, the CLI performs the following steps:
Fetch Docker Manifest
The CLI retrieves the image’s manifest and configuration from the registry.
This includes:
Image layers (SHA digests)
Extract and Identify Layers
All layer digests listed in the manifest are collected and treated as “packages” for curation evaluation.
Run Curation Rules on Each Layer
Each layer is checked against the configured policy conditions.
Example:
