Working with Nested Components

As an Application Developer, you use nested Components to execute a single deployment process where multiple Components are deployed on the same Deployment Target. This helps you to, for example, keep track of the sub-components when deploying a Kubernetes Application using Helm.

Nested Components can also be used to deploy one Component that needs to get multiple Artifacts from different Artifact Sources. Nested Components can overcome the 1-1 assignment limit of Component-Artifact mapping in one Package.

To deploy nested Components, you have to assign them to a normal Component and deploy the normal Component. Several nested Components can be assigned to a normal Component. However, deploying a normal Component with assigned nested Components does not necessarily mean that all nested Components are deployed. You can define which nested Components should be deployed by adding the Select Nested Components Action to the Component Workflow.

Notes:

Viewing Nested Components

Nested Components can be accessed:

Creating Nested Components

To create a nested Component, the same procedure as for Creating Components can be used. The nested type is defined by the baseType parameter set in the Component custom type.

Assigning Nested Components to a Parent Component

Nested Components can be assigned:

Deleting Nested Components

To delete a nested Component, the same procedure for Deleting Components can be used.

You can also delete nested Components from the Application dashboard:

  1. Double-click an Application to open the Application dashboard.
  2. Select a Component.
  3. Click the delete button in the Nested Components section of the right sidebar.

Dynamic Properties

You can use the @parent type to reference dynamic properties of the parent Component.

Example:

{@parent/system/name}

See also: