Fix for - JFrog cli issue #2851 #1396
Merged
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
shahiinn
approved these changes
Jun 6, 2025
amithins
approved these changes
Jun 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Link to github issue : jfrog/jfrog-cli#2851
Issue description : We are facing this issue during config transfer process, when virtual repository associated with default deployment repository. With the current code, we are removing the repositoryRefs and not the default deployment repository. In Artifactory, we have a condition check, the default deployment repository should be part of repositoryRefs, because of which we are encountering this issue.
Code fix implemented : We are removing both repositoryRefs and default deployment repository during the repository creation process. Later, we are adding it back again during update repository process. Virtual repository transfer process is designed in such a way ( creation + updation ) to overcome this issue #822.