fix-show updated env values in request - #140
Open
rajashreehj-bruno wants to merge 1 commit into
Open
Conversation
princek-bruno
approved these changes
Aug 25, 2026
rajashreehj-bruno
force-pushed
the
VSCODE-130-get-updated-env-variables
branch
from
September 1, 2026 11:53
dd3e902 to
c9c3a47
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Jira: VSCODE-130
Problem
When secret is configured, it's not getting updated immediately in requests
Fix
Instead of getting cached env data, live data is used to get the env data so secret configured will be available immediately to request.