Greg Anderson

Related: https://github.com/jhedstrom/drupalextension/pull/220

Is this still an issue? I thought that https://github.com/jhedstrom/drupalextension/pull/220 cleared this problem up.

Also, tangentially related, to avoid a lint error in the example I replaced: ``` const loadersKey = "dataloaders" ``` With: ``` type key int const ( loadersKey key = iota...

That doesn't look correct to me. You should be using dots to access config. The underscores might work accidentally with environment variables, but you should be using dot-separated terms for...

I have not looked up what options Terminus Build tools itself defines, but you should be using that as your exemplar. @danielbachhuber's scenario 1 example is in the right form.

Nested config has definitely worked in the past. I don't see why it would have stopped working.

Build tools documents [some configuration options](https://github.com/pantheon-systems/terminus-build-tools-plugin#configuration); it does not document environment variable equivalence. We're also missing documentation on environment variable overrides in [the consolidation/config README](https://github.com/consolidation/config). Terminus `self:config:dump` does not understand...

Environment variable overrides for config is [implemented here](https://github.com/consolidation/config/blob/master/src/Util/EnvConfig.php#L42,L47). For Terminus, the prefix is `TERMINUS`, so if there was config: ``` terminus: foo: bar:value ``` That would map to `TERMINUS_FOO_BAR` rather...

The problem may in fact be in the memory of the commenter (moi)

I guess that `${env-name}` is already replaced in most instances, but is not replaced when running drush sa? The [drush 9](https://github.com/pantheon-systems/terminus/blob/69d352be4e92851ff4e7d64253b27b5282071f17/templates/aliases/policy/Commands/PantheonAliasPolicyCommands.php) version of this policy file will also need to...