feat: add support for remote-repo-url UNIFY-506 #646
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
adrobuta
force-pushed
the
feat/container-remote-repo-url
branch
from
596557b to
fb8de2d
Compare
neil-snyk
previously approved these changes
Mar 4, 2025
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
gergo-papp
force-pushed
the
feat/container-remote-repo-url
branch
from
fb8de2d to
802479f
Compare
adrobuta
force-pushed
the
feat/container-remote-repo-url
branch
from
802479f to
b4e9de6
Compare
Contributor
|
@adrobuta do you still need a review for this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Adds support for remote-repo-url option for ContainerTarget.
Remote-repo-url allows the user to override the remote URL for the image that is monitored/tested.
Monitoring container images using remote-repo-url groups container images under the same target with other monitored projects.
Where should the reviewer start?
How should this be manually tested?
Any background context you want to provide?
What are the relevant tickets?
https://snyksec.atlassian.net/browse/UNIFY-506
Screenshots
Additional questions