Automation Suite
2023.10
false
- Overview
- Requirements
- Installation
- Prerequisite checks
- Downloading the installation packages
- uipathctl cluster
- uipathctl cluster maintenance
- uipathctl cluster maintenance disable
- uipathctl cluster maintenance enable
- uipathctl cluster maintenance is-enabled
- uipathctl cluster migration
- uipathctl cluster migration export
- uipathctl cluster migration import
- uipathctl cluster migration run
- uipathctl cluster upgrade
- uipathctl config
- uipathctl config add-host-admin
- uipathctl config additional-ca-certificates
- uipathctl config additional-ca-certificates get
- uipathctl config additional-ca-certificates update
- uipathctl config alerts
- uipathctl config alerts add-email
- uipathctl config alerts remove-email
- uipathctl config alerts update-email
- uipathctl config argocd
- uipathctl config argocd ca-certificates
- uipathctl config argocd ca-certificates get
- uipathctl config argocd ca-certificates update
- uipathctl config argocd generate-dex-config
- uipathctl config argocd generate-rbac
- uipathctl config argocd registry
- uipathctl config argocd registry get
- uipathctl config argocd registry update
- uipathctl config enable-basic-auth
- uipathctl config orchestrator
- uipathctl config orchestrator get-config
- uipathctl config orchestrator update-config
- uipathctl config saml-certificates get
- uipathctl config saml-certificates rotate
- uipathctl config saml-certificates update
- uipathctl config tls-certificates
- uipathctl config tls-certificates get
- uipathctl config tls-certificates update
- uipathctl config token-signing-certificates
- uipathctl config token-signing-certificates get
- uipathctl config token-signing-certificates rotate
- uipathctl config token-signing-certificates update
- uipathctl health
- uipathctl health bundle
- uipathctl health check
- uipathctl health diagnose
- uipathctl health test
- uipathctl manifest
- uipathctl manifest apply
- uipathctl manifest diff
- uipathctl manifest get
- uipathctl manifest get-revision
- uipathctl manifest list-applications
- uipathctl manifest list-revisions
- uipathctl manifest render
- uipathctl prereq
- uipathctl prereq create
- uipathctl prereq run
- uipathctl resource
- uipathctl resource report
- uipathctl snapshot
- uipathctl snapshot backup
- uipathctl snapshot backup create
- uipathctl snapshot backup disable
- uipathctl snapshot backup enable
- uipathctl snapshot delete
- uipathctl snapshot list
- uipathctl snapshot restore
- uipathctl snapshot restore create
- uipathctl snapshot restore delete
- uipathctl snapshot restore history
- uipathctl snapshot restore logs
- uipathctl version
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
uipathctl manifest apply
Automation Suite on EKS/AKS Installation Guide
Last updated Apr 19, 2024
uipathctl manifest apply
Load the configuration found at PATH, and apply it to the cluster.
The command performs a diff between the current state of the cluster and the desired state, and applies the changes to the cluster.
When the
--override
flag is present, the list overrides the selection found in the input file. The flag is mutually exclusive with the --only
flag. When the exclude_components
key is present in the input file, the components found in the list are excluded from the installed components. This has the
highest priority over all the other flags and it is not mutually exclusive with any of them.
uipathctl manifest apply PATH [flags]
uipathctl manifest apply PATH [flags]
# Apply the configuration found in input.json, using the versions found in versions.json
uipathctl manifest apply input.json --versions versions.json
# Apply the configuration and specify the kubeconfig file to use
uipathctl manifest apply input.json --kubeconfig cluster.kubeconfig --versions versions.json
# Simulate the apply command and print on stdout the result of the operation
uipathctl manifest apply --dry-run input.json
# Apply the configuration but skip the components installed directly by helm
uipathctl manifest apply --skip-helm input.json --versions versions.json
# Apply the configuration overriding the initial list of components
uipathctl manifest apply --override automation_hub,orchestrator --versions versions.json
# Apply the configuration found in input.json, using the versions found in versions.json
uipathctl manifest apply input.json --versions versions.json
# Apply the configuration and specify the kubeconfig file to use
uipathctl manifest apply input.json --kubeconfig cluster.kubeconfig --versions versions.json
# Simulate the apply command and print on stdout the result of the operation
uipathctl manifest apply --dry-run input.json
# Apply the configuration but skip the components installed directly by helm
uipathctl manifest apply --skip-helm input.json --versions versions.json
# Apply the configuration overriding the initial list of components
uipathctl manifest apply --override automation_hub,orchestrator --versions versions.json
--continue-on-error if true, continue applying the manifest even if an error occurs
--dependencies-only if true, only dependencies will be applied
--dry-run if true, just print the result of the command, without applying it
--fail-on-version if true, fail if the version of the component is not found in the versions file
-h, --help help for apply
--no-wait if true, return immediately after the ArgoCD applications are created
--only strings optional exclusive list of components to apply
--override strings optional list to override the components enabled in input.json file
--skip-dependencies if true, dependencies will be skipped
--skip-helm if true, skip components installed directly by helm
--versions string optional path to versions file
--continue-on-error if true, continue applying the manifest even if an error occurs
--dependencies-only if true, only dependencies will be applied
--dry-run if true, just print the result of the command, without applying it
--fail-on-version if true, fail if the version of the component is not found in the versions file
-h, --help help for apply
--no-wait if true, return immediately after the ArgoCD applications are created
--only strings optional exclusive list of components to apply
--override strings optional list to override the components enabled in input.json file
--skip-dependencies if true, dependencies will be skipped
--skip-helm if true, skip components installed directly by helm
--versions string optional path to versions file
--context string name of the kubeconfig context to use
--kubeconfig string kubectl configuration file (default: ~/.kube/config)
--log-format string log format. one of [text,json] (default "text")
--log-level string set log level. one of [trace,debug,info,error] (default "error")
--timeout duration timeout of the command (default 1h0m0s)
--context string name of the kubeconfig context to use
--kubeconfig string kubectl configuration file (default: ~/.kube/config)
--log-format string log format. one of [text,json] (default "text")
--log-level string set log level. one of [trace,debug,info,error] (default "error")
--timeout duration timeout of the command (default 1h0m0s)