Deprecation: Top level 'properties' in addons are deprecated. Please define 'properties' at the job level.
search cancel

Deprecation: Top level 'properties' in addons are deprecated. Please define 'properties' at the job level.

book

Article ID: 413958

calendar_today

Updated On:

Products

VMware Tanzu Application Service VMware NSX

Issue/Introduction

  • The warning as shown below may show up in Apply Changes logs: /ops_manager_apply_changes_logs/deployment/install_log.txt
    Deprecation: Top level 'properties' in addons are deprecated. Please define 'properties' at the job level.
  • This comes from a change in the BOSH Director’s manifest schema that affects how addons are defined in deployment manifests or cloud configs.
  • The code where the warning is defined: Github

Environment

Bosh director 
VMware NSX

Cause

This warning is indicating that there is a syntax error in runtime-config files present in the environment. To check this, use bosh configs command to see the list of configs and the bosh config <number of a config> to review its contents. 

The warning is indicating that a properties object is not under the job level object. 

Example incorrect syntax is as shown:

addons:
- name: syslog
  jobs:
  - name: syslog_forwarder
    release: syslog
  properties:
    syslog:
      address: 10.0.0.1

Correct syntax:

addons:
- name: syslog
  jobs:
  - name: syslog_forwarder
    release: syslog
    properties:
      syslog:
        address: 10.0.0.1

Resolution

A runtime-config file(s) present in the environment have incorrect syntax. 

The deprecation warning comes from the BOSH Director’s manifest validation logic, introduced in newer versions (starting around BOSH Director v271+).
It’s warning you that your manifest still uses the old structure.

To stop the warning from appearing upgrade the release to a version that’s BOSH Director schema–compliant.

Additional Information

A similar warning:

"Global 'properties' are deprecated. Please define 'properties' at the job level."

may appear if the syntax issue is in the deployment manifest Github