Fix: Export globals paramter in Run via CLI if user has selected any global environment #8559
+3
−2
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.
Changes

Fix the issue that when user activates any global environment, Run Via CLI has not exported the globals Inso parameter.
Currently, if user has selected any global environment and click Run Via CLI, the selected global environment will not be exposed in CLI preview.
As a result, Inso will use the active global environment in the workspace. But if user has selected other global environment in the current workspace later, the active global environment will be changed. This will make the environment context different from what user is expecting.
Fix this issue by expose active global environment parameter together.