CORE-385: exclude azure libs from CRL #422
Merged
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
|
davidangb
requested review from
dvoet and
marctalbott
and removed request for
a team
This was referenced Mar 31, 2025
dvoet
approved these changes
Mar 31, 2025
marctalbott
approved these changes
Mar 31, 2025
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.
https://broadworkbench.atlassian.net/browse/CORE-385 is a security finding on
json-smart.json-smartis pulled in bycom.azure:azure-identity, which is pulled in bybio.terra:terra-cloud-resource-lib. However, RBS doesn't need those Azure libs.This PR excludes the Azure libs from CRL, which in turn excludes
json-smart.Part of a group of PRs: