mirror of https://github.com/docker/cli.git
6bcfa8806c
As for top-level key, any 3rd-level key which starts with `x-` will be ignored by compose. This allows for users to: * include additional metadata in their compose files * create YAML anchor objects that can be re-used in other parts of the config This matches a similar feature in the swagger spec definition: https://swagger.io/specification/#specificationExtensions This means a composefile like the following is valid ``` verison: "3.7" services: foo: image: foo/bar x-foo: bar network: bar: x-bar: baz ``` It concerns services, volumes, networks, configs and secrets. Signed-off-by: Vincent Demeester <vincent@sbr.pm> |
||
|---|---|---|
| .. | ||
| config_schema_v3.0.json | ||
| config_schema_v3.1.json | ||
| config_schema_v3.2.json | ||
| config_schema_v3.3.json | ||
| config_schema_v3.4.json | ||
| config_schema_v3.5.json | ||
| config_schema_v3.6.json | ||
| config_schema_v3.7.json | ||