configFile is a domain field on environments, components, and tasks. Deployah records and inherits the path. It does not mount the file.
Runtime env is a different concept and must stay separate:
envFile -> FileValues -> {fullname}-env -> envFrom
env: -> ExplicitValues -> container env:
Do not reuse {fullname}-env or a generic chart configMap.data for this. The unused generic Helm ConfigMap path was removed so it would not constrain this feature.
When this is implemented, design the Kubernetes representation from configFile itself. A dedicated {fullname}-config ConfigMap plus a volume mount is a likely shape, not a decision.
Open questions for that design:
- one file or several
- how environment, component, and task layers combine
- merge vs replace
- ConfigMap key / filename
- directory mount vs subPath
- checksum / rollout
- hook tasks and
deployah run
- whether binaryData ever matters
Until then the field stays in the spec, schema, init, and docs as a recorded path that is not delivered.
configFileis a domain field on environments, components, and tasks. Deployah records and inherits the path. It does not mount the file.Runtime env is a different concept and must stay separate:
Do not reuse
{fullname}-envor a generic chartconfigMap.datafor this. The unused generic Helm ConfigMap path was removed so it would not constrain this feature.When this is implemented, design the Kubernetes representation from
configFileitself. A dedicated{fullname}-configConfigMap plus a volume mount is a likely shape, not a decision.Open questions for that design:
deployah runUntil then the field stays in the spec, schema, init, and docs as a recorded path that is not delivered.