Nicolas De loof
Nicolas De loof
> It is already difficult to update / change anything related to the CLI config due to its broad usage internally and externally to Docker. Sure, but they already do....
oh indeed, I guess it's to late to complain on https://github.com/docker/compose/issues/2383 that the compose attribute should align with CLI flags 🥲
Thanks a lot for your contribution. Please run `npm run format` to fix CI
I guess this issue is fixed by https://github.com/docker/node-sdk/pull/47/files#diff-406198e18bb578d844d48953e9187cb6a344bf35063fa9d29e7efbec88c39c25R452-R455 WDYT ?
Normalization is required as project name is used as prefix for docker resources, so those restrictions. `.` anyway should not be an issue, need to check if there's any other...
`environment` is managed internally using the `KEY=VALUE` representation during the merge phase, this is why `!reset` doesn't work here. Not sure how this could be fixed... > would be nice...
Had to re-read the original issue description, there's actually something weird as 3 yaml files get merged, the last one using `!reset`. If I only use 2 of those the...
My initial diagnostic was right: during yaml merge process, `envrionment` is converted to use the KEY=VALUE syntax (this is the only way we can merge even without interpolation). So after...
@hablutzel1 this is a bug, not to be documented but fixed, while I'm not sure "how" yet
env file management is a risky area, we got a bunch of regression any time we introduced changes there, even those considered reasonable. For this reason, I'm closing this as...