-
Bug
-
Resolution: Cannot Reproduce
-
Undefined
-
None
-
MTA 8.0.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
None
Description of problem:
Discovery on Cloud Foundry manifest with multiple applications fails
Version-Release number of selected component (if applicable):
MTA 8.0.0
How reproducible:
Always
Steps to Reproduce:
$mta-cli discover cloud-foundry --input=./2_apps.yaml
INFO[0000] Using manifest path for Cloud Foundry local discover manifest_path=./2_apps.yaml
INFO[0000] Processing file. filename=./2_apps.yaml
INFO[0000] Warning: manifest file does not contain a name file_path=./2_apps.yaml
Error: no app name found in manifest file ./2_apps.yaml (edited)
Here's the Cloud Foundry manifest used.
$cat 2_apps.yaml
version: 1
applications:
name: my-app-1 # This application will be selected
memory: 512M
instances: 2
buildpacks: [java_buildpack]
env:
DATABASE_URL: postgres://...
name: my-app-2 # This application will be ignored
memory: 256M
instances: 1
buildpacks: [java_buildpack]
Actual results:
Discovery fails
Expected results:
Discovery should succeed and discovery manifest should be generated.