UiPath Documentation
uipath-cli
latest
false
Guide de l'utilisateur de UiPath CLI
Important :
Ce contenu a été traduit à l'aide d'une traduction automatique. La localisation du contenu nouvellement publié peut prendre 1 à 2 semaines avant d’être disponible.

Déploiement d'applications codées uip

Syntaxe et options de `uip codedapp deploy`, qui déploie ou met à niveau une application Web codée publiée dans UiPath.

uip codedapp deploy deploys or upgrades a published app in UiPath. When the app is already deployed, the command upgrades it in place; otherwise it checks that the path name is free and deploys the app. It targets the latest published version by default; pass --version to pin a specific build. Use --folder-key to pick the destination folder.

Synthèse​

uip codedapp deploy [options]
uip codedapp deploy [options]

Options​

DrapeauDescription
-n, --name <name>App name. Converted to the package ID the same way as in pack. When omitted, the name saved in the local app configuration is used; in an interactive terminal without a saved name, the command prompts for it.
--display-name <name>Human-readable app title shown in UiPath. When omitted, the title remembered from an earlier deploy is used, then --name as typed. On an upgrade, only an explicit --display-name renames the deployed app.
--path-name <name>App pathname in the URL (https://<org>.uipath.host/<path-name>). Defaults to the app name. On an upgrade, the path name changes only when you pass this option. To check whether a path name is free, run uip codedapp validate --path-name.
--client-id <id>Remplacement de l’ID de client OAuth (client non confidentiel/public).
-v, --version <version>Cibler une version publiée spécifique. La valeur par défaut est la dernière version publiée.
--tags <tags>Des étiquettes de catégorisation séparées par des virgules pour l'application déployée, par exemple governance,insights.
--base-url <url>URL de base UiPath (remplacer l'authentification).
--org-id <id>ID de l’organisation (remplissage d’authentification).
--org-name <name>Nom de l'organisation (remplissage d'authentification).
--tenant-id <id>ID de locataire (remplissage d’authentification).
--folder-key <key>Folder key to deploy into. Refer to Folder selection.
--access-token <token>Jeton d’accès (remplacer l’authentification).

Folder selection​

The destination folder is resolved in this order:

  1. --folder-key, when passed. If the app was published into your Personal Workspace, a shared folder key is refused; if it was published into the tenant feed, a Personal Workspace folder key is refused.
  2. The UIPATH_FOLDER_KEY environment variable.
  3. The folders available to your account, filtered to Personal Workspace or shared folders to match how the app was published. When exactly one folder matches, it is selected automatically. When several match, an interactive terminal shows a picker; a non-interactive run fails and asks for --folder-key. Run uip or folders list --output json to find a folder key.

Exemples​

# Deploy / upgrade to the latest published version
uip codedapp deploy --name "MyApp"

# Pin a specific version
uip codedapp deploy --name "MyApp" --version "1.0.0"

# Deploy into a folder
uip codedapp deploy --name "MyApp" \
    --folder-key f0f0f0f0-0000-0000-0000-000000000001

# Separate display title, a custom OAuth client, and system tags
uip codedapp deploy --name "my-app" --display-name "My App" \
    --client-id "my-oauth-client-id" --tags governance
# Deploy / upgrade to the latest published version
uip codedapp deploy --name "MyApp"

# Pin a specific version
uip codedapp deploy --name "MyApp" --version "1.0.0"

# Deploy into a folder
uip codedapp deploy --name "MyApp" \
    --folder-key f0f0f0f0-0000-0000-0000-000000000001

# Separate display title, a custom OAuth client, and system tags
uip codedapp deploy --name "my-app" --display-name "My App" \
    --client-id "my-oauth-client-id" --tags governance

Format des données (--sortie json)​

{
  "Code": "DeployCompleted",
  "Data": { "message": "App deployed successfully." }
}
{
  "Code": "DeployCompleted",
  "Data": { "message": "App deployed successfully." }
}

A failed deploy returns Result: "Failure" with Message: "Deploy failed" and the cause in Instructions.

Modes d’échec​

  • External application token without Apps scopes. When you sign in with an external application (client credentials) whose token carries no Apps scope, the UiPath Apps service rejects the request. The command fails with ErrorCode: "permission_denied" and a message naming the Apps.Read and Apps.Write scopes. Grant both scopes to the external application, add them to uip login --scope, and sign in again.
  • Path name already taken. A fresh deploy fails when the path name is in use in the organization. Pass a different --path-name.
  • Folder key required. A non-interactive run with several candidate folders and no --folder-key or UIPATH_FOLDER_KEY fails.
  • App not published. The command fails when no published version of the app (or of the --version you passed) is found. Run uip codedapp publish first.

Voir également​

Cette page vous a-t-elle été utile ?

Connecter

Besoin d'aide ? Assistance(opens in new window)

Vous souhaitez apprendre ? UiPath Academy(opens in new window)

Vous avez des questions ? UiPath Forum(opens in new window)

Rester à jour