search

micahhausler / container-tx

container-transform in go
MIT License
10 stars 1 forks source link

Have it understand `extends` #4

Open TylerRick opened 6 years ago

TylerRick commented 6 years ago

It looks like it's currently just ignoring any extends directives in compose files.

Expected: I would expect it to either read in the file referenced by extends in the same way docker-compose does or give an error asking you to use docker-compose config if it detects the file contains extends.

Could even have it read in docker-compose.yml (and docker-compose.override.yml if present) by default for compose input type, the same way docker-compose does... though perhaps it's fine to keep it explicit, esp. given that the docker-compose config option is so easily available.

micahhausler commented 6 years ago

I think trying to re-implement the docker-compose merge logic could get a little hairy, and it'd be hard to make sure it was always consistent with how docker-compose behaves. I'm not opposed to barfing and telling the user to give the merged input (or subshelling and getting the input of docker-compose config) instead.