DCAE spec schema to be updated to include following properties

1) log_directory  - Each MS owner should expose log directory the application logs will be written into. This will be used by DCAE platform during deployment to expose this into log sidecar.

The bp-gen should use this config and create following property in the blueprint

      log_info:

        log_directory: "/opt/app/VESCollector/logs/ecomp"

(Reference - https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-ves.yaml-template?h=casablanca)

2) use_tls flag - DCAE platform relies on components to indicate if it should be enables for TLS (in which case healthcheck api will be https) and also components are required to specify the directory where ONAP cert should be distributed).

tls_info:{{   }}

    cert_directory: '/opt/app/dh/etc/cert/'         

        use_tls: true

 This info should be derived from spec

3) Certain MS require ENV variables to be exposed during deployment. Platform support env list specified under cloudify.interfaces.lifecycle:starts:inputs; need provision in spec file to be used for driving the corresponding bp

   https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-hv-ves.yaml-template

4) Certain DMAAP DR subscribers supports decompression and privileged subscription. These are used for improving robustness. Currently there is no way to identify these in spec file.

  https://git.onap.org/dcaegen2/services/pm-mapper/tree/dpo/blueprints/k8s-pm-mapper.yaml

5) Also require in spec to identify the required policy_model_id  (DCAEGEN2-1867)

6) Postgres plugin integration related properties.

    example - https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-holmes-rules.yaml-template