Defining MTA Extension Descriptors
The Multitarget Application (МТА) extension descriptor is a YAML file that contains data complementary to the deployment descriptor. This data can be without a lifecycle, specially encoded, and security-sensitive like credentials and passwords. The MTA extension descriptor is a YAML file that has the same structure as the deployment descriptor. It can add or overwrite existing data if necessary.
Several extension descriptors can be additionally used after the initial deployment.
In the examples below, we have a deployment descriptor, which has already been defined, and several extension descriptors.
The following example is a basic extension descriptor that extends the deployment descriptor above:
The example above instructs SAP Cloud Platform to:
- Validate the extension descriptor against the MTA specification version 3.1
- Extend the com.example.extension deployment descriptor
The following is a modification to the extension descriptor that adds data and overwrites data in the extension descriptor:
The above instructs SAP Cloud Platform to:
- Extend the deployment descriptor by its ID
- Overwrite the data for the existing-data property
- Add a new data called non-existing-data to the data-storage properties
The following is an example of another extension descriptor that extends the extension descriptor from the previous example:
The example above instructs the SAP Cloud Platform to:
- Extend the first extension descriptor by its ID
- Add a new data called second-non-existing-data to the data-storage properties
- The examples above are incomplete. To deploy a solution, you have to create a deployment descriptor and an MTA archive.
As of _schema version 3.1, you have the option to input missing values that are required by the Multitarget Application, which afterwards act as the latest provided MTA extension descriptor. During deployment using the cockpit the SAP Cloud Platform detects the missing values, and opens a dialog where you can enter them. This option can be useful when you need to extend already provided MTAs with new data.
For example, you can choose to provide credentials manually instead of storing and providing them in an MTA extension descriptor file. Also, you can manually input subaccount-relevant parameter values, specific to the provider or consumer subaccount in the provider-consumer scenario. For more information, see the Supported Metadata Options subsection of MTA Module Types, Resource Types, and Parameters for Applications in the Neo Environment.