Deployer Extensions

Deployer extensions describe how Greentic can deploy a bundle without baking every target into application packs. A deployer can target local development, Docker or Podman, Kubernetes, Terraform, AWS, Azure, GCP, private clouds, or a custom enterprise deployer.

A deployer extension declares a greentic.deployer.v1 contract and is authored with the gtdx CLI as a deploy extension.

Contract Shape

greentic.deployer.v1 is not a greentic.ext.capabilities.v1 offer list. It has its own validated contract:

pack.yaml

extensions:
  greentic.deployer.v1:
    kind: greentic.deployer.v1
    version: 1.0.0
    inline:
      schema_version: 1
      planner:
        flow_id: flows/plan.ygtc
      capabilities:
        - capability: plan
          flow_id: flows/plan.ygtc
        - capability: apply
          flow_id: flows/apply.ygtc
        - capability: destroy
          flow_id: flows/destroy.ygtc
        - capability: status
          flow_id: flows/status.ygtc
        - capability: rollback
          flow_id: flows/rollback.ygtc

Supported deployer capabilities are:

• generate
• plan
• apply
• destroy
• status
• rollback

Validation requires schema_version: 1, a non-empty planner flow_id, non-empty capability flow_id values, no duplicate capability entries, and at least the plan capability.

Create One with gtdx

Scaffold a deployer extension with the gtdx CLI:

gtdx new my-deployer --kind deploy
gtdx dev

gtdx new --kind deploy scaffolds the extension project and its describe.json manifest. See Writing Extensions for the inner loop and Publishing Extensions for signing and distribution.

What a Deployer Does

A deployer extension normally provides one or more flows:

• a planner flow that turns bundle configuration into a deployment plan
• an apply flow that performs the deployment
• a status flow that reports deployment state
• optional generate, destroy, or rollback flows

This keeps deployment separate from business flows. The same application bundle can be planned locally, applied to Kubernetes, deployed to one of the major clouds, or handed to a platform-team deployer selected by the operator.

Validate

Check the extension before publishing:

gtdx validate .          # describe.json against its JSON Schema
gtdx lint                # cross-field invariants beyond JSON Schema
gtdx publish --dry-run   # full build + pack + validate, no registry write

See Publishing Extensions for the full validation and signing flow.