Moved Golang remote registry setting logic from security-cli to cli-core #1128
Conversation
This file contains 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
attiasas
reviewed
Feb 15, 2024
attiasas
added
improvement
…solution-from-artifactory-golang
eranturgeman
had a problem deploying
to
frogbot
GitHub Actions
Failure
eranturgeman
added
ignore for release
…solution-from-artifactory-golang
eranturgeman
changed the title
…solution-from-artifactory-golang
…golang' into resolution-from-artifactory-golang
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.
This PR introduces an new function that enables setting an Artifactory server as dependencies resolution registry for Golang projects.
This logic previously existed in security-cli, and got removed from there in this PR: jfrog/jfrog-cli-security#21