fix: prevent assigning incorrect resource ID for sensitive variables with same name, type and at least one matching scope #605
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
…that share same name, type and at least one matching scope. Problem: When multiple sensitive variables with same name, type, description and different scope are created, if one of their scoping matches then the id of incorrect variable is being used to set the Resource ID. Solving this by making sure all the scopes are also matched for sensitive variables so that appropriate variable id is assigned to Resource ID.
|
Thanks for this PR @bshaik1. we will review it over the next few days |
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.
Problem: When multiple sensitive variables with same name, type, description and different scope are created, if one of their scoping matches then the id of incorrect variable is being used to set the Resource ID.
Related to this issue: #212
Solving this by making sure all the scopes are also matched for sensitive variables so that appropriate variable id is assigned to Resource ID.