Compositions

The Composition is the canonical, reviewable form of an infrastructure change. In the CloudBooster portal it appears as a tab on the ChangeSet review screen, alongside the ADR and Diagram tabs.

It's the layer you read — and occasionally edit — before approving.

What you'll see

When you open the Composition tab, you see a list of components. Each component has a type, a name, and a set of inputs. Components can reference each other, and the portal renders those references inline.

The Diagram tab is generated from the Composition. The Provider plan tab is too. Edit the Composition and both re-render on Re-preview.

A short example

components:
  - type: aws:network/vpc@v1
    name: api-staging-vpc
    inputs:
      cidr: 10.20.0.0/16
      public_subnets: 2
 
  - type: aws:db/postgres@v1
    name: api-db
    inputs:
      network: api-staging-vpc
      size: db.t4g.medium
      storage_gb: 50

Editing in the portal

The Composition tab is editable. You can adjust component inputs — instance size, bucket name, retention days — and click Re-preview to regenerate the Diagram and Provider plan.

CloudBooster validates your edits against the component schema. If an input is the wrong type, a required field is missing, or a reference points at a component that doesn't exist, the portal flags it inline and refuses to move the ChangeSet to Approved until it's resolved.

Where it comes from

• Proposing a change in the portal produces a Composition from your intent.
• Importing an existing Terraform or Pulumi stack produces one from its state.
• The portal can produce one from a guided flow.

Whatever the origin, the Composition you review in the portal is the same artifact.

See also

• ChangeSets — the lifecycle that wraps every Composition.
• Review a ChangeSet — the operational how-to.