- 概要
- はじめに
- 概念
- UiPath CLI を使用する
- 使用ガイド
- CI/CD レシピ
- コマンド リファレンス
- 概要
- 終了コード
- グローバル オプション
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- add-test-data-entity
- テスト データのキューを追加
- 追加-テスト-データ-バリエーション
- 分析
- 開発
- プロジェクトを作成
- 差分
- アクティビティを検索
- GET-ANALYZER-RULES
- get-default-activity-xaml
- エラーを取得
- 手動テスト用のテスト ケースを取得
- 手動テストステップを取得
- get-library-object-repository
- get-object-repository
- get-versions
- Get-workflow-example
- indicate-application
- 要素を示す
- inspect-package
- install-data-fabric-entities
- パッケージのインストールまたは更新
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- パッケージ化
- パブリッシュ
- remote
- 元に戻す
- run, debug & execution
- ファイル名を実行
- 検索テンプレート
- スタートスタジオ
- 実行を停止
- tm
- UIA
- uip tasks
- uip traces
- uip traces feedback
- 移行
- 参照とサポート
Syntax and options for `uip config`, which reads, sets, and clears CLI configuration preferences stored in config.json.
uip config reads and writes the CLI's local configuration file — defaults like the output format, log level, and the version/update-channel policy that governs uip update and uip tools update. The file is discovered by walking up from the current directory to $HOME looking for .uipath/config.json, falling back to ~/.uipath/config.json if none is found; --config-file overrides discovery for any verb.
概要
uip config get [key] [-c <path>]
uip config set <key> <value> [-c <path>]
uip config clear <key> [-c <path>]
uip config get [key] [-c <path>]
uip config set <key> <value> [-c <path>]
uip config clear <key> [-c <path>]
All uip config verbs honor the global options (--output, --output-filter, --log-level, --log-file). Exit codes follow the standard contract.
Config keys
| キー | Valid values | Writable | 説明 |
|---|---|---|---|
output | table、json、yaml、plain、markdown | ○ | Default output format for CLI commands. |
logLevel | error、warn、info、debug | ○ | Default log level. |
interactive | neverauto、always | ○ | When the CLI may show interactive prompts. Defaults to auto. |
updateChannel | stable, preview (dev is accepted but not advertised) | ○ | Release channel used to resolve tool updates. |
version | major.minor or major.minor.patch (e.g. 1.2 or 1.2.3) | ○ | Version policy: an exact major.minor.patch freezes auto-update entirely; a major.minor line tracks that line; unset follows the latest release. |
clientSecret | — | × | External app client secret used by uip login. Read-only from uip config — set it via uip login --client-secret env.NAME so the secret stays in an environment variable and the auth file, never in config.json. |
Two older keys, autoVersionSync and versionSource, were removed when the version policy was collapsed into version + updateChannel. Running uip config set autoVersionSync ... or versionSource ... now fails with Unknown config key, and the error message steers you to the version/updateChannel equivalent.
uip config get
Get one configuration value, or the full configuration when no key is given.
引数
| 名前 | Required | 目的 |
|---|---|---|
[key] | × | One of the config keys above. Omit to show the entire config file. |
オプション
-c, --config-file <path>— path to a specific config file, overriding discovery.
例
uip config get output
uip config get output
# Show everything
uip config get
# Show everything
uip config get
データシェイプ(--output json)
シングルキー:
{
"Code": "ConfigGet",
"Data": { "Key": "output", "Value": "table" }
}
{
"Code": "ConfigGet",
"Data": { "Key": "output", "Value": "table" }
}
A key with no value set returns Value: "-". clientSecret (and any other secret-bearing key) always returns <redacted>, never the real value.
No key — the full file, secrets redacted:
{
"Code": "ConfigList",
"Data": {
"Config": {
"core": { "output": "table", "logLevel": "info", "updateChannel": "stable" },
"auth": { "clientId": "client-abc", "clientSecret": "<redacted>" }
}
}
}
{
"Code": "ConfigList",
"Data": {
"Config": {
"core": { "output": "table", "logLevel": "info", "updateChannel": "stable" },
"auth": { "clientId": "client-abc", "clientSecret": "<redacted>" }
}
}
}
ConfigGet and ConfigList are distinct Code values so a JMESPath consumer sees one stable shape per Code rather than a Data field that changes shape depending on whether key was passed.
uip config set
Set a configuration value.
引数
| 名前 | Required | 目的 |
|---|---|---|
<key> | ○ | A writable config key (all of the keys above except clientSecret). |
<value> | ○ | The new value. Validated against the key's allowed values, when it has one. |
オプション
-c, --config-file <path>— path to a specific config file, overriding discovery. The file is created if it doesn't exist.
例
uip config set output table
uip config set output table
uip config set updateChannel preview
uip config set updateChannel preview
# Pin the CLI and tools to the 1.196 line (float — tracks patch releases within it)
uip config set version 1.196
# Freeze on an exact patch (no auto-update at all)
uip config set version 1.196.3
# Pin the CLI and tools to the 1.196 line (float — tracks patch releases within it)
uip config set version 1.196
# Freeze on an exact patch (no auto-update at all)
uip config set version 1.196.3
データシェイプ(--output json)
{
"Code": "ConfigSet",
"Data": { "Key": "output", "Value": "table", "Status": "Updated" }
}
{
"Code": "ConfigSet",
"Data": { "Key": "output", "Value": "table", "Status": "Updated" }
}
Attempting to set clientSecret fails with ValidationError pointing you to uip login --client-secret env.NAME instead. An invalid value for an enumerated key (for example uip config set output csv) fails with ValidationError and lists the valid values.
uip config clear
Remove a configuration value. A no-op (not an error) if the key was never set.
引数
| 名前 | Required | 目的 |
|---|---|---|
<key> | ○ | A writable config key. |
オプション
-c, --config-file <path>— path to a specific config file, overriding discovery.
例
# Un-pin the version so the CLI follows the latest release again
uip config clear version
# Un-pin the version so the CLI follows the latest release again
uip config clear version
# Clearing a key that was never set is a no-op
uip config clear updateChannel
# Clearing a key that was never set is a no-op
uip config clear updateChannel
データシェイプ(--output json)
{
"Code": "ConfigClear",
"Data": { "Key": "version", "Status": "Cleared" }
}
{
"Code": "ConfigClear",
"Data": { "Key": "version", "Status": "Cleared" }
}
Status is "Not set" instead of "Cleared" when the key had no value to remove.
関連
- uip update —
config get version/config set versiongovern which lineuip updateanduip tools updateresolve against. - uip tools — tool installs/updates read the same
versionandupdateChannelkeys. - uip login — sets credentials outside
config.json;clientSecrethere is read-only for a reason.