cpln apply command creates or updates Control Plane resources from JSON or YAML files, enabling infrastructure-as-code workflows.
When to use this
GitOps workflows
Store resource definitions in Git and apply them in CI/CD pipelines
Reproducible deployments
Apply the same configuration across multiple environments
Bulk operations
Create or update multiple resources in a single command
Scripting & automation
Automate resource management in scripts and pipelines
Basic usage
Specifying the GVC
For resources that belong to a GVC (Identity, Volume Set, Workload), specify the GVC using one of these methods:- In your profile
- With --gvc flag
- In the resource file
Set a default GVC in your profile:All subsequent commands will use this GVC.
You can specify either a
gvc property in the file or use the --gvc flag, but not both.Apply Kubernetes manifests
Convert and apply Kubernetes resources directly:Apply from stdin
Pipe resource definitions from another command:Using the console
The console also supports applying resources:- Click the cpln apply button in the upper right corner
- Upload a JSON/YAML file or paste the resource definition
- Select the target org and GVC
- Click Apply
Multiple resources
Apply multiple resources in a single file by separating them with---:
If a resource references another resource (e.g., a workload references a GVC), the referenced resource must be defined in the same file unless it already exists.
Resource ordering
Thecpln apply command handles resource ordering automatically — you do not need to worry about the order of resources in your files or directories. The CLI resolves dependencies internally.
Renaming resources
Changing a resource’sname in the file creates a new resource. The original resource remains and must be deleted manually:
Limitations
Agents
Agents
To create an agent, use the console or CLI
agent command to obtain the bootstrap config data. The cpln apply command does not output config data.Cloud accounts
Cloud accounts
Before creating a cloud account, additional configuration is required at the cloud provider. See the Create Cloud Account guide.
Domains
Domains
Before creating a domain, the required DNS entries must exist. See the Configure a Domain guide.
Generate sample input
Export existing resources as templates:- Console
- CLI
- Select a resource and click Actions → Export
- Choose JSON Slim or YAML Slim
- Download the file
Use in GitOps
Theapply command integrates with CI/CD pipelines for GitOps workflows. See the CI/CD Usage guides for details.
Example templates
Use these templates as starting points for your resource definitions.Download all examples: cpln-apply-examples.zip
Agent
Agent
Cloud Accounts
Cloud Accounts
Cloud Accounts Reference Page
Cloud Account - AWS
Cloud Account - AWS
Cloud Account - Azure
Cloud Account - Azure
Cloud Account - GCP
Cloud Account - GCP
Cloud Account - NGS
Cloud Account - NGS
Domains
Domains
Secrets
Secrets
Secrets Reference Page
Secret - AWS
Secret - AWS
Secret - Azure Connector
Secret - Azure Connector
Secret - Azure-SDK
Secret - Azure-SDK
Secret - Dictionary
Secret - Dictionary
Secret - Docker
Secret - Docker
Secret - ECR
Secret - ECR
Secret - GCP
Secret - GCP
Secret - KeyPair
Secret - KeyPair
Secret - Opaque
Secret - Opaque
Secret - TLS
Secret - TLS
Secret - Username/Password
Secret - Username/Password
Groups
Groups
Policies
Policies
Policies Reference PageEach
targetKind has its own set of permissions. Get them via:- CLI:
cpln secret permissions - Reference: Secret Permissions
Policy - Explicit Secret
Policy - Explicit Secret
Policy - All Secrets
Policy - All Secrets
Identities
Identities
Workloads
Workloads
Next steps
CI/CD Usage
Automate deployments in CI/CD pipelines
Convert K8s Manifests
Convert Kubernetes resources to Control Plane
GitOps
Infrastructure as code workflows
Apply Command Reference
Full apply command reference