Support reading config from stdin

[dnephin]

Related to #1377

By supporting configuration from stdin, it becomes a lot easier for users with complex templating requirements to use a separate tool for templating, and pass the final config into docker-compose directly.

I wanted to ensure that the if filename == '-' check only happened in one place, so I had to refactor some of compose.cli.command. get_config_path was moved to compose.config to support this.

[aanand]

I think I'd find this bit of logic less confusing if it were moved into the function above. At that point, I think the functions' responsibilities are a bit better-separated, and they could also be renamed. Say:

defresolve_config_details(base_dir, filename):
iffilename=='-':
returnConfigDetails(yaml.safe_load(sys.stdin), os.getcwd(), None)
iffilenameisNone:
file_path=find_config_file(base_dir)
else:
file_path=os.path.join(base_dir, filename)
returnConfigDetails(load_yaml(file_path), os.path.dirname(file_path), file_path)
deffind_config_file(base_dir):
(candidates, path) =find_candidates_in_parent_dirs(SUPPORTED_FILENAMES, base_dir)
# ...

[dnephin]

I had just copied the old get_config_path() from Command, but now that we have another place to move it, I think that makes sense.

[aanm]

So it won't be possible to use a compose-file and stdin at the same time? This would be interesting when people want to overwrite stuff from compose-file without creating a new file. Such as:

$cat my-compose.yml web:
ports: 1234:5000
$ docker-compose up -f my-compose.yml --stdin-extends '{web: {ports: 5000:5000}}'

Which would result in running web with ports 5000:5000 instead of 1234.
(I know the format is wrong but you get the idea ;-) )

[dnephin]

@aanm that's correct, the stdin would replace the file. I think this is pretty standard for unix utilities. If you need something from a file, it would be up to you to read the original file, and merge it into the final config you send to stdin.

[aanand]

@aanm What you describe is interesting (and partly covered by the extends option), but orthogonal to the idea of reading input from stdin - it'd apply just as much in the case of having two files, rather than one file + stdin.

@dnephin Come to think of it, what's the behaviour of extends in config read from stdin? Looks like it'll resolve paths relative to the current directory, but that should be documented somewhere.

[dnephin]

True, I should add that with the small doc change I made about using - for file.

[aanm]

@aanand I thinking that could some some users problems when they want to scale
something like:

count=0
whiletrue;let count=count+1
docker-compose up -f my-compose.yml --stdin-extends '{web: {ports: $count:5000}}'do

My point is too use environment variables has input for configuration in compose. I think that would solve some problems that users are getting.

@dnephin Does docker itself has this feature that you are PR?

[aanand]

@aanm For environment variable interpolation, see #1377.

[dnephin]

Updated the docs, and cleaned up get_config_path()

[dnephin]

Rebased again! Should be ready

[aanand]

LGTM