You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have no centralized way of overriding config in the case of env variable or command-line flag.
This has lead to pieces scattered across the codebase that approach things in a non-uniform manner, in addition they often rely on env variables, and are therefore prone to environmental issues during testing.
Bring defaulting into a central location.
The text was updated successfully, but these errors were encountered:
Fixes#4202#2481
Moves defaulting logic from hard coded section in config init to a central location that uses transformers.
Previously `dev` mode was operating against the configuration object model. This meant that it would sometimes replace pieces of configuration where really it should just have modified it.
Now dev mode will override the following in the yaml config, but it will leave any adjacent configuration as it was:
```yaml
homepage:
enabled: false
include_subgraph_errors:
all: true
plugins:
experimental.expose_query_plan: true
sandbox:
enabled: true
supergraph:
introspection: true
telemetry:
tracing:
experimental_response_trace_id:
enabled: true
```
Currently we have no centralized way of overriding config in the case of env variable or command-line flag.
This has lead to pieces scattered across the codebase that approach things in a non-uniform manner, in addition they often rely on env variables, and are therefore prone to environmental issues during testing.
Bring defaulting into a central location.
The text was updated successfully, but these errors were encountered: