Repository navigation
allow optional env_file for include top level #13719
Description
Activity
I have moved onto other projects. If in the future this feature gets accepted feel free to use my draft PR (rough proposal) as a starting point.
Proposal:
Suggested behavior:
- Continue supporting current behavior
- Add optional support for
formatandrequired
Affected repositories:
- Compose-go
- Compose-spec
- Compose
- Other projects?
Suggested changes:
- compose-spec: point include.env_file at the existing #/$defs/env_file definition in the schema, and document it in 14-include.md
- compose-go: sync the schema and implement the behavior (rough draft of changes if reader was curious )
- docker/compose: bump compose-go
Questions:
IncludeConfigis an exported type so changingStringListto[]EnvFilecould cause issues- If so should this be handled in any specific way i.e marking it deprecated, adding a new/second
EnvFilelike property so both behaviors can be used etc...
- If so should this be handled in any specific way i.e marking it deprecated, adding a new/second
Description
in #3560 optional env files are allowed at a service level https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/#additional-information
however this env file https://docs.docker.com/reference/compose-file/include/#env_file doesnt support being optional would it be possible to also make include level env_files optional using the same syntax?