Separate env params extraction by context #432
Merged
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.
Bug description:
ScanRepository params validation interfere with ScanPullRequest command while trying to get branches related params.
Fix:
Env params extraction should behave different depending on command context.
We assume the context of the command by the pull request ID param. If it is set, we assume we are in ScanPullRequest context, otherwise we are in ScanRepository context.
When in the context of ScanPullRequest, no need to extract branches related env vars.
In the context of ScanRepository, extract branches, git templates and aggregate fixes flag, which are all unrelated to the second context.