Daniel Nephin 3a43110f06 Fix a bug in ExtendsResolver where the service name of the extended service was wrong. ... This bug can be seen by the change to the test case. When the extended service uses a different name, the error was reported incorrectly. By fixing this bug we can simplify self.signature and self.detect_cycles to always use self.service_name. Signed-off-by: Daniel Nephin <dnephin@docker.com>		2015-11-12 13:54:41 -05:00
..
circle-1.yml	Fix a bug in ExtendsResolver where the service name of the extended service was wrong.	2015-11-12 13:54:41 -05:00
circle-2.yml	Fix a bug in ExtendsResolver where the service name of the extended service was wrong.	2015-11-12 13:54:41 -05:00
common.yml
docker-compose.yml
invalid-links.yml
invalid-net.yml
invalid-volumes.yml
nested-intermediate.yml
nested.yml
no-file-specified.yml
nonexistent-path-base.yml
nonexistent-path-child.yml
nonexistent-service.yml
service-with-invalid-schema.yml
service-with-valid-composite-extends.yml
specify-file-as-self.yml
valid-common-config.yml
valid-common.yml
valid-composite-extends.yml
valid-interpolation-2.yml
valid-interpolation.yml
verbose-and-shorthand.yml