App::env() + parseEnv() improvements #17794
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.
Description
craft\helpers\App::env()now supports parsing nested environment variables, e.g.FOO="bar/${BAZ}".craft\helpers\App::parseEnv()now supports parsing nested environment variables using the…/$NAME/…and…${NAME}…syntaxes anywhere within the passed-in string (not just beginning with$NAME/…).CRAFT_SITEandCRAFT_SITE_UPPERenvironment variables are now defined when the current site is determined.CRAFT_SITEis set to the site’s handle.CRAFT_SITE_UPPERis set to the site’s handle, converted to UPPER_SNAKE_CASE.So for example, it’s now possible to define per-site API token environment variables, such as:
…and then reference each of them dynamically, depending on the current site, by setting an API token setting to:
Related issues