anchor.diff:      server.port: 9090
   ----
   
  +If the package defines multiple applications, provide the name of the package in the top level YML section to scope the `spec` section.  That is, given a multiple application package with the layout
  +
  +----
  +ticktock-1.0.0/
  +├── packages
  +│   ├── log
  +│   │   ├── package.yml
  +│   │   └── values.yml
  +│   └── time
  +│       ├── package.yml
  +│       └── values.yml
  +├── package.yml
  +└── values.yml
  +
  +----
  +A top level `values.yml` file
  +
  +----
  +hello: world
  +
  +time:
  +  appVersion: 1.3.0.M1
  +  deployment:
  +    applicationProperties:
  +      log.level: WARN
  +      trigger.fixed-delay: 1
  +log:
  +  deployment:
  +    count: 2
  +    applicationProperties:
  +      log.level: WARN
  +      log.name: skipperlogger
  +----
  +
  +Would set `hello` as a variable available to be used as a placeholder in the `packages\log\values.yml` file and the `packages\time\values.yml`.  However, the YML section under `time:` is applied only to the `packages\time\values.yml` file and the YML section under `log:` is applied only to the `packages\time\values.yml` file.
  +
  +
  +
  +
  +
   
   [[package-upload]]
  -== Package Upload
  +=== Package Upload
   
   After creating the package in the above structure, we can compress it in a zip file with the name
   [PackageName]-[PackageVersion].zip e.g. mypackage-1.0.0.zip
  
positive.code: All the applications inside the `mypackagegroup`  are considered sub-packages and would follow the similar package
  structure as the individual packages.
  These sub packages need to be specified inside the `packages` directory of the root package `mypackagegroup`.
  
  
  [[package-metadata]]
  
negative.code: Deployer implementations.
  
  [[package-values]]
  === Package Values
  
  The `values` YAML file contains the default values for any of the keys specified in the template files.
  
  For instance, in a package that defines one application, the format is
  
  ----
  version: 1.0.0.RELEASE
  