uipath-cli
latest
false
UiPath-CLI-Benutzerhandbuch
- Überblick
- Erste Schritte
- Konzepte
- Verwenden der UiPath CLI
- Anleitungen
- CI/CD-Rezepte
- Befehlsreferenz
- Überblick
- Exitcodes
- Globale Optionen
- UIP-codierter Agent
- uip coder
- uip context-grounding
- UIP-Dokumentation
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- Add-Test-Data-Entität
- Add-Test-Data-Queue
- Add-Test-Data-Variation
- Analysieren
- Erstellen
- Ein Projekt erstellen
- Diff
- Suchaktivitäten
- Get-Analyse-Regeln
- get-standard-aktivität-xaml
- Fehler abrufen
- Manuelle-Testfälle erhalten
- Manuelle-Testschritte erhalten
- get-library-object-repository
- get-object-repository
- Get-Versionen
- Beispiel für einen Workflow abrufen
- Anwendung anzeigen
- Anzeigeelement
- Inspektionspaket
- install-data-fabric-entities
- Pakete installieren oder aktualisieren
- list-data-fabric-entities
- list-instances
- Beispiele für Listenworkflows
- Packen
- Veröffentlichen
- remote
- restore
- run, debug & execution
- Ausführungsdatei installieren
- Suchvorlagen
- Studio starten
- Ausführung anhalten
- tm
- UIA
- uip tasks
- UIP-Ablaufverfolgungen
- uip traces feedback
- Migration
- Referenz und Support
Wichtig :
Dieser Inhalt wurde maschinell übersetzt.
Es kann 1–2 Wochen dauern, bis die Lokalisierung neu veröffentlichter Inhalte verfügbar ist.
Syntax and options for `uip maestro flow publish`, which packs a Flow project and uploads the resulting `.nupkg` directly to Orchestrator packages.
uip maestro flow publish packs a Flow project directory and uploads the resulting .nupkg to Orchestrator packages in one step — a shortcut for uip maestro flow pack followed by a manual upload.
Zusammenfassung
uip maestro flow publish <project-path> [output-path] [-n <name>] [-v <version>] [--feed-id <id> | --folder-key <key> | --folder-path <path>]
uip maestro flow publish <project-path> [output-path] [-n <name>] [-v <version>] [--feed-id <id> | --folder-key <key> | --folder-path <path>]
Honors global options. Exit codes follow the standard contract. Requires uip login.
Argumente
<project-path>(erforderlich) – Der Pfad zum Flow-Projektverzeichnis (mussproject.uiprojund mindestens eine.flow-Datei enthalten).[output-path](optional) — directory where the generated.nupkgis written before upload. Defaults to a temp directory (<os-tmpdir>/flow-publish-<timestamp>).
Optionen
| Option | Standard | Beschreibung |
|---|---|---|
-n, --name <name> | project folder name | Paketname. |
-v, --version <version> | 1.0.0 | Paketversion |
--feed-id <feedId> | Mandanten-Feed | Target feed ID. Mutually exclusive with --folder-key/--folder-path. |
--folder-key <key> | – | Orchestrator folder key (GUID) whose folder-hierarchy feed to publish into — the CLI resolves the feed ID automatically. Mutually exclusive with --feed-id/--folder-path. |
--folder-path <path> | – | Orchestrator folder path, e.g. Shared/Sub — resolved to a feed ID the same way as --folder-key. Mutually exclusive with --feed-id/--folder-key. |
Beispiele
# Pack and publish to the tenant feed
uip maestro flow publish ./my-flow-project --version 1.2.0
# Publish into a specific folder's feed
uip maestro flow publish ./my-flow-project --folder-key c3d4e5f6-… --version 1.2.0
# Pack and publish to the tenant feed
uip maestro flow publish ./my-flow-project --version 1.2.0
# Publish into a specific folder's feed
uip maestro flow publish ./my-flow-project --folder-key c3d4e5f6-… --version 1.2.0
Datenform (--output json)
{
"Code": "FlowPublish",
"Data": {
"Package": "my-flow-project@1.2.0",
"PackagePath": "/tmp/flow-publish-1710000000000/my-flow-project.flow.Flow.1.2.0.nupkg",
"Upload": [
{ "key": "my-flow-project.flow.Flow.1.2.0.nupkg", "status": "Created" }
]
}
}
{
"Code": "FlowPublish",
"Data": {
"Package": "my-flow-project@1.2.0",
"PackagePath": "/tmp/flow-publish-1710000000000/my-flow-project.flow.Flow.1.2.0.nupkg",
"Upload": [
{ "key": "my-flow-project.flow.Flow.1.2.0.nupkg", "status": "Created" }
]
}
}
Upload[].status is "Created" the first time a given package version is uploaded, or the feed's own conflict status on a repeat upload of the same name/version.
Siehe auch
uip maestro flow pack— pack only, without uploadinguip maestro flow init– erstellen Sie zuerst ein Gerüst für das Projektuip maestro flow process— run the published process- Flow-Übersicht