Is it any option to define download folder name in Monaco v2 (Yaml is ignored)

[Slawa]

After each launch: monaco download -v --environment prod-env-1
new random folder is created
manifest:

manifestVersion: 1.0
projects:
  - name: prod
    path: shared/prod
environmentGroups:
  - name: prod
    environments:
      - name: prod-env-1
        url:
          type: value
          value: https://xxxxx.dynatrace.com/
        auth:
          token:
            name: YOUR_TOKEN_ENV_VAR

[AntonPineiro · Accepted solution]

Hi,

Yes, but not in YAML file, it is an argument to download command. You can specify with "--output-folder":

Best regards

[Slawa]

Yes, I am using this flags: 

monaco download -v --environment dt-prod-env -o dt-group -f -p prod

But I am a bit confused for what is this part in YAML

projects:
  - name: prod
    path: shared/prod
environmentGroups:
  - name: prod
    environments:
      - name: prod-env-1

 if it totally ignored?
E.g. 
this one config replaced automatically by download with autogenerated:

manifestVersion: "1.0"
projects:
- name: prod
environmentGroups:
- name: default
  environments:
  - name: prod

Based on docs I am expecting - this will be a project struscture as defined in YAML
https://www.dynatrace.com/support/help/manage/configuration-as-code/configuration

[Radoslaw_Szulgo]

Yes, it is. The configuration in YAML is taken by "deploy" command rather than download.

[AntonPineiro]

Hi,

You define projects and environments in the YAML file.

And you choose which projects are deployed in which environments.

Projects paths are not in relation to download configurations, they are in relation where are target YAML and JSON files to be deployed.

Following your example.

• manifest.yaml.
• shared/prod directory.
• shared/prod/config.yaml.
• shared/prod/template.json.

If you type:

monaco deploy manifest.yaml -p prod -e prod-env-1

If will deploy that project in that environment. You can omit project, to deploy all projects; omit environment, to deploy to all environments.

Best regards

[Slawa]

Thanks for clarification, 
so download ignored all of project settings apart the env name (declared in cli argument).

Strange solution: not follow Yaml file structure during download, but follow during deploy

Just a bit misleading documentation where file structure is binded with Yaml file: