validate fails to identify missing disk property

[gilzow]

Related to testing in #145, after correcting the mount source_path issue, validate failed to identify that I had added a mount, but had not added a disk property to the config, which resulted in

  E: Error parsing configuration files:
      - applications./.platform.app.yaml: The application "platformify_cookies" is diskless but defines local mounts and such mounts require disks. This means the configuration has to have a "disk" key with an integer value greater or equal to 128.

when attempting to push the change.

[akalipetis]

Thanks for reporting @gilzow - currently we only validate the static schema - this is a dynamic property and should definitely be handled in the future.

[akalipetis]

This should also take into account things like missing service names, etc.

For example (submitted by @devicezero):

Add a service:

    mounts:
      "/foobar":
        source: "service"
        source_path: "foobar"

Pushing the code will fail validation on the git side with:

 E: Error parsing configuration files:
    - applications.config.yaml:express.mounts./foobar: When source is 'service', a service name is required. Set `service: <service name>` to specify the service that will provide the networked mount.