cpln apply
is a good way to leverage the CLI in an idempotent manner.apply
command is called by executing:
FILE_NAME
is the path for the file and it can be either a JSON or YAML file containing the resource metadata.
To apply an Identity, a Volume Set or a Workload resource you need to specify a GVC using one of the following methods.
gvc
within your cpln profile. This will add the gvc
to the session context of the profile and will be refered to as the default gvc
when executing any future command including the cpln apply
command.
--gvc
flag to the apply
command. This will pass the gvc
as an option and will override the default gvc
that is defined in the profile.
gvc
property in the resource definition within the file you intend to apply.
--gvc
flag, but not both.apply
command.
--k8s true
option to the apply
command, the K8s resources will be converted and applied.
apply
command utilizes the logic of the CLI convert command and then applies the resulting output.
stdin
(Standard Input), use the following command.
cpln apply
command.cpln apply
button in the upper right corner of the console. A modal will be displayed containing the upload instructions.
The cpln apply modal provides the ability to specify in which org
and gvc
a resource will be executed. The default is your currently selected org
and gvc
.
A file or an input containing an Identity, a Volume Set or a Workload resource will be executed in the scope of the specified gvc
in the cpln apply modal. In case a gvc
is defined within a resource, the resource will be executed in the scope of that gvc
.
cpln apply
command will create a new resource.
NOTE: Any orphaned resources will need to be manually deleted.
cpln apply
command from the CLI or console does not output the config data.cpln gvc get GVC_NAME -o yaml-slim --org ORG_NAME
will output the GVC_NAME as YAML.json-slim
and yaml-slim
format options will output only the necessary values needed for a subsequent call to the cpln apply
command.apply
command can be used to manage Control Plane resources as part of a CI/CD pipeline.
Refer to the GitOps CLI documentation for additional information.
Agent
Cloud Accounts
Cloud Account - AWS
Cloud Account - Azure
Cloud Account - GCP
Cloud Account - NGS
Domains
Secrets
Secret - AWS
Secret - Azure Connector
Secret - Azure-SDK
Secret - Dictionary
Secret - Docker
Secret - ECR
Secret - GCP
Secret - KeyPair
Secret - Opaque
Secret - TLS
Secret - Username/Password
Groups
Policies
all
. The targetLinks
and targetQuery
properties are not evaluated.Each ‘targetKind’ has its own unique set of binding permissions. The permissions can be obtained by:cpln secret permissions
), orPolicy - Explict Secret
Policy - All Secrets