1f7faadc77
Refactors config validation of a service to use a ServiceConfig data object. Instead of passing around a bunch of related scalars, we can use the ServiceConfig object as a parameter to most of the service validation functions. This allows for a fix to the config schema, where the name is a field in the schema, but not actually in the configuration. My passing the name around as part of the ServiceConfig object, we don't need to add it to the config options. Fixes #2299 validate_against_service_schema() is moved from a conditional branch in ServiceExtendsResolver() to happen as one of the last steps after all configuration is merged. This schema only contains constraints which only need to be true at the very end of merging. Signed-off-by: Daniel Nephin <dnephin@docker.com> |
||
|---|---|---|
| .. | ||
| cli | ||
| config | ||
| __init__.py | ||
| const.py | ||
| container.py | ||
| legacy.py | ||
| progress_stream.py | ||
| project.py | ||
| service.py | ||
| state.py | ||
| utils.py | ||