Commits on May 31, 2018

1. 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>

   

   vdemeester committed May 31, 2018
   Configuration menu

   • View commit details
   • Copy full SHA for 6bcfa88
   • Browse repository at this point

   Copy the full SHA

   6bcfa88 View commit details

   Browse the repository at this point in the history