bg-deploy different result with option -e

[Dominik-Gehrig]

Description

Dear mta-cli colleagues,

I try to deploy my meta-app with an extension file. When I run the following commands I get different results:

success scenario:

1. mbt build -p=cf -e ./extensions/extension.mtaext --mtar=service.mtar
2. cf bg-deploy ./mta_archives/service.mtar --no-confirm

error scenario:

1. mbt build -p=cf --mtar=service.mtar
2. cf bg-deploy ./mta_archives/servicve.mtar -e ./extension/extension.mtaext --no-confirm

MTA.yaml

`modules:

Node Server

• name: my-app
  type: custom
  path: gen/srv
  build-parameters:
  builder: custom
  ignore: ["jest.*"]
  commands:
  - npm install --omit=dev
  parameters:
  memory: 1024M
  buildpack: nodejs_buildpack
  domain: cert.${default-domain}
  requires:
  • name: my-dependent-service
    parameters:
    path: ./my-cert.json
    `

MTAEXT.matext

modules: - name: my-app requires: - name: my-depndent-service parameters: path: ./my-new-space-dep-cert.json

My assumption is that both scenarios behave equally. Unfortunately the second scenario doesn't merge the extension file with the mta file properly.

Your environment

• MultiApps Controller version - 3.2.2
• MultiApps CF CLI Plugin version - 3.2.2
• which CF vendor is used - SAP BTP Cloud Foundry

•  MTA Build Tools 1.2.28
  

Steps to reproduce

Additional information

[theghost5800]

Hi @Dominik-Gehrig , mbt tool and multiapps cli plugin are two separate tools. MBT tool is used during build time of mta project while Multiapps cli plugin is used during deployment time. During deployment time all specified extension descriptors are uploaded to the backend side - multiapps-controller and they are merged and used on the backend side.

Here you can find documentation about extension descriptors in the case when they are passed during deployment time. As I can see from provided extension descriptor example, specifying path to file with parameters inside extension descriptor is not supported during deployment time. All configuration files during mta deployment must be part of generated mtar file. To be able to pass some additional configurations inside extension descriptors during deployment, they must be embedded inside of the yaml file.