[feature request] recognize docker-compose.<something>.yml files

[waspinator]

Docker compose has an option to override files for use in different situations. A common pattern seems to be to append a .<something> to a docker-compose file. Could we add recognition of those type of files?

https://docs.docker.com/compose/extends/#example-use-case

[chrisdias]

what are you thinking about when you say "recognition"? According to the docs, a docker-compose.override.yml will automatically be picked up. If you have another file then you have to pass them to docker-compose with multiple -f parameters. There is no way to easily specify the order of files in VS Code. I could have a multiple pick list, but there is no explicit order with that.

tell me more what you would like to see... thx.

[waspinator]

It's not a big deal I know, but I'd like to see a pink whale instead of an exclamation mark as the file icon. I'm not sure if any actual linting is happening to the docker-compose file, but if it is, having the whale icon gives me more confidence that vscode knows what kind of file it is.

[robertpeteuil]

This is related to a request I made in January in #206

[AArnott]

@chrisdias As #223 describes, the docker-compose.override.yml file will only be automatically picked up if no -f switch is specified. This VS Code Docker extension's UI forces us to specify exactly one yml file, which turns into a -f switch. This means no file is automatically picked up, and no single file has the right content for local development, since local development is facilitated by docker-compose.yml and docker-compose.override.yml combined.

[PrashanthCorp]

@AArnott, it looks like the -f switch is specified by default. See here.

Would the gist of your request be that this flag be made optional?

[AArnott]

Yes.

[StephenWeatherford]

@PrashanthCorp Please pull last issue into a separate bug.

[StephenWeatherford]

Should enter an issue against vscode.

[bwateratmsft]

Marking this one as a dupe of #379 and #520