Deployment Task Document
Last updated
Last updated
Normally you want to document what needs to be deployed. One process, multiple processes, with dependend components (e.g. process routes) etc. A deployment task document would be required.
Create a deployment task document that lists all components that must be deplyoed together with a parent component.
/c the components for which to create a deploymen task document. You may also provide multiple components or a component package, as mentioned abouve
(see Common Arguments).
/DeployableOnly restricts the considered components to deployable componentes: Processes, Certificates, Services, Process Routes, APIs.
Maps, Profiles are not deployable and therefore skipped.
/Children=Independent Get only children which have an independent relationship to their parent(s) - the <compId>. Only those child components require a separate deployment. Sub-Processes (not routes), for example, are dependent components and not deployed separately.
/t specifies the that is used to render a nice document.
The deployTask.mdtemplate renders a nice Markdown output that you can hand over to your deployment admin.
