[FEATURE] extract metadata with dependencies: auto-create deployment package / CSCLSROZ-60

[JoernBerkefeld]

idea: almost all types depend on other metadata to be deployed alongside. We want to be able to to point to, say, an automation, and then copy the automation plus all dependencies into a staging folder that the user can then ready for actual deployment.

 

the same logic can then later be re-used for templating.

 

acceptance criteria:

option 1

• new command prepare
• command outputs warning that it uses local files and not server files
• interactively ask for source
• interactively ask for target
• supported types:
  • automation (folder, activities)
  • automation activities (folder, data extension, ...)

option 2 (#1134)

• Ask if dependencies should be included
• Show multiselect list (all pre-selected)
• Ask for target CRED and Bu
• Copy to deploy folder
• Ask if deploy should be executed

option 3 (#69)

• buildTemplate uses subroutine from prepare to fetch correct dependent data
• dependent metadata is downloaded
• supported types:
  • automation (folder, activities)
  • automation activities (folder, data extension, ...)

Dependencies

• [TASK] Rewrite dependency variables to r__ format / CSCLSROZ-329 #58

[JoernBerkefeld]

decided to go with option 3 (buildTemplate) first and re-open the ticket associated with option 2 for a later release

[github-actions]

Closed by #1441.