Restricting usage in ConfigProfile with Xray version prior to 3.117.0 #834
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
eranturgeman
changed the title
eranturgeman
added
improvement
github-actions
bot
removed
the
safe to test
eranturgeman
added
the
safe to test
github-actions
bot
removed
the
safe to test
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 a new limitation for utilizing Config Profile - Xray version must be 3.117 or above.
If Xray version is lower than 3.117 and you wish to utilize config profile with the new abilities introduced here jfrog/jfrog-cli-security#314 you can either upgrade Xray or use prior Frogbot version until Xray version is upgraded.
Note: This restriction is valid ONLY when utilizing Config Profile. Other capabilities are not changed or blocked due to this restriction