refactor: make env marker config available through target and flag #2853
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.
This factors creation of (most of) the env marker dict into a separate target and
provides a label flag to allow customizing the target that provides it.
This makes it easier for users to override how env marker values are computed. The
env_marker_setting
rule will still, if necessary, compute values from the toolchain,but existing keys (computed from the env marker config target) have precedence.
The
EnvMarkerInfo
provider is the interface for implementing a custom env markerconfig target; it will be publically exposed in a subsequent PR.
Along the way, unify how the env dict and defaults are set.
Work towards #2826