DockerCLI/cli/compose/schema
Vincent Demeester 6bcfa8806c
Allow `x-*` extension on 3rd level objects
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>
2018-05-31 13:38:58 +02:00
..
data Allow `x-*` extension on 3rd level objects 2018-05-31 13:38:58 +02:00
bindata.go Allow `x-*` extension on 3rd level objects 2018-05-31 13:38:58 +02:00
schema.go Replace go-bindata with esc 2018-02-12 14:23:19 -05:00
schema_test.go Allow `x-*` extension on 3rd level objects 2018-05-31 13:38:58 +02:00