Refactor config validation to support constraints in the same jsonschema
Reworked the two schema validation functions to read from the same schema but use different parts of it. Error handling is now split as well by the schema that is being used to validate. Signed-off-by: Daniel Nephin <dnephin@docker.com>
This commit is contained in:
parent
be554c3a74
commit
dc3a5ce624
5 changed files with 87 additions and 95 deletions
|
|
@ -31,8 +31,8 @@ from .types import ServiceLink
|
|||
from .types import VolumeFromSpec
|
||||
from .types import VolumeSpec
|
||||
from .validation import match_named_volumes
|
||||
from .validation import validate_config_section
|
||||
from .validation import validate_against_config_schema
|
||||
from .validation import validate_config_section
|
||||
from .validation import validate_depends_on
|
||||
from .validation import validate_extends_file_path
|
||||
from .validation import validate_network_mode
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue