astronomer / astro-cli / 9754dc36-2798-478e-9835-21fe399566dd

45%

main: 45%

Pull #2170

circleci

fix: Forward host environment to the compose loader so bare env passthrough resolves

astro dev start (Docker mode) builds its Compose project with
loader.LoadWithContext but left ConfigDetails.Environment unset. compose-go
resolves the bare host-env passthrough form (environment: [VAR] /
build.args: [VAR], with no value) by looking the variable name up in that
project Environment mapping (loader/environment.go resolveServicesEnvironment,
loader/normalize.go) -- a path separate from ${VAR} interpolation. With the
mapping empty, every bare passthrough silently resolved to nothing, diverging
from the plain docker compose CLI (which forwards the host environment) and from
astro's own standalone mode.

${VAR} interpolation was unaffected because it already used
Interpolate.LookupValue = os.LookupEnv.

Set Environment: composetypes.NewMapping(os.Environ()) on both ConfigDetails
literals (createDockerProject and createDockerProjectWithPorts) so bare
passthrough resolves to the host value, matching docker compose. A host
variable still reaches a container only when explicitly declared in the compose
YAML, so there is no new leakage surface.

1 of 2 new or added lines in 1 file covered. (50.0%)

25418 of 56370 relevant lines covered (45.09%)

7.81 hits per line