automation-suite
2023.10
false
- Überblick
- Vor der Installation
- Installation
- Clusterverwaltung
- uipathctl-Cluster
- uipathctl-Clusterwartung
- 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 config add-host-admin
- uipathctl config argocd
- uipathctl config argocd registry
- uipathctl config argocd registry get
- uipathctl config argocd registry update
- uipathctl-Version
- Sichern und Wiederherstellen
- uipathctl-Snapshot
- uipathctl-Snapshot-Sicherung
- 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
- Zertifikatverwaltung
- uipathctl config additional-ca-certificates
- uipathctl config additional-ca-certificates get
- uipathctl config additional-ca-certificates update
- uipathctl config argocd ca-certificates
- uipathctl config argocd ca-certificates get
- uipathctl config argocd ca-certificates update
- uipathctl config saml-certificates
- 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
- Aktualisierung
- Authentication
- Überwachung und Warnungen
- Produktspezifische Konfiguration
- Fehlersuche und ‑behebung
uipathctl manifest apply
Wichtig :
Es kann 1–2 Wochen dauern, bis die Lokalisierung neu veröffentlichter Inhalte verfügbar ist.

uipathctl-Referenzhandbuch
Letzte Aktualisierung 24. Feb. 2025
uipathctl manifest apply
Laden Sie die unter PATH gefundene Konfiguration und wenden Sie sie auf den Cluster an.
Der Befehl führt einen Vergleich zwischen dem aktuellen Status des Clusters und dem gewünschten Status durch und wendet die Änderungen auf den Cluster an.
Wenn das Flag
--override
vorhanden ist, überschreibt die Liste die in der Eingabedatei gefundene Auswahl. Das Flag schließt sich gegenseitig mit dem Flag --only
aus. Wenn der exclude_components
-Schlüssel in der Eingabedatei vorhanden ist, werden die in der Liste gefundenen Komponenten von den installierten Komponenten ausgeschlossen. Dies hat die höchste Priorität vor allen anderen Flags und schließt sich gegenseitig nicht aus.
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/cluster_config.json --versions versions.json
# Apply the configuration and specify the kubeconfig file to use
uipathctl manifest apply input.json/cluster_config.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/cluster_config.json --versions versions.json
# Apply the configuration but skip the components installed directly by helm
uipathctl manifest apply --skip-helm input.json/cluster_config.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/cluster_config.json --versions versions.json
# Apply the configuration and specify the kubeconfig file to use
uipathctl manifest apply input.json/cluster_config.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/cluster_config.json --versions versions.json
# Apply the configuration but skip the components installed directly by helm
uipathctl manifest apply --skip-helm input.json/cluster_config.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/cluster_config.json file
--skip-dependencies if true, dependencies will be skipped
--skip-helm if true, skip components installed directly by helm
--versions string 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/cluster_config.json file
--skip-dependencies if true, dependencies will be skipped
--skip-helm if true, skip components installed directly by helm
--versions string 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)