Path map environment variable values #26609
Open
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.
Apart from threading through
PathMapper
togetEffectiveEnvironment
, this required refactoring away theenvResolved
logic inEnhancedStarlarkAction
andExtraAction
. Instead,ActionSpawn
now always calls out togetEffectiveEnvironment
to resolve the env, while giving subclasses ofSpawnAction
a chance to override it.RELNOTES: The values of environment variables are now subject to path mapping (if enabled for the action).