uip solution resource

uip solution resource inventories the resources (queues, assets, buckets, processes, connections) that a local solution depends on — the ones declared in each project's bindings_v2.json and aggregated into the solution's resource list. Use it to see what the solution will need when deployed, or to re-sync the solution inventory after editing project bindings.

Remarque :

Not to be confused with uip resource

This page documents the resource subcommand of uip solution — a local, solution-scoped inventory tool.

The standalone uip resource tool is a different command: it provides CRUD over Orchestrator's server-side queues, assets, buckets, etc. on a live tenant.

Rule of thumb: uip solution resource inspects files on disk, uip resource talks to Orchestrator.

Synopsis

uip solution resource <verb> [options]

Verbs

Verb	Objectif
list	List resources in the solution — local, remote, or both.
refresh	Re-scan projects and sync the solution's resource inventory from their bindings_v2.json files.

Both verbs honor the global options (--output, --output-filter, --log-level, --log-file). Exit codes follow the standard contract.

uip solution resource list

List resources in the solution. By default, returns both the resources declared locally in the solution manifest and the resources that Orchestrator reports for the associated remote tenant. Use --source to narrow to one side; use --kind and --search to filter.

When both sides are listed, remote entries that match a local entry by Kind:Name (case-insensitive) are deduplicated — the local entry wins.

Arguments

Nom	Requis	Objectif
[solutionPath]	non	Path to the solution directory. Defaults to the current directory.

Options

Short	Long	Valeur (Value)	Default	Description
—	--kind	ENUM	—	Queue, Asset, Bucket, Process, Connection. Case-insensitive.
—	--search	text	—	Contains-match on resource name.
—	--source	ENUM	all	all, local, or remote.

Exemples

# All resources the current solution knows about
uip solution resource list

# Only queues declared locally
uip solution resource list --kind Queue --source local

# Remote buckets whose name matches "invoice"
uip solution resource list --kind Bucket --search invoice --source remote

# Point at a specific solution directory
uip solution resource list ./solutions/finance

Data shape (--output json)

{
  "Code": "ResourceList",
  "Data": [
    {
      "Source": "Local",
      "Key": "a1b2c3d4-0000-0000-0000-000000000001",
      "Name": "InvoiceIntake",
      "Kind": "Queue",
      "Type": "",
      "Folder": "Shared"
    },
    {
      "Source": "Remote",
      "Key": "b2c3d4e5-0000-0000-0000-000000000002",
      "Name": "InvoiceBucket",
      "Kind": "Bucket",
      "Type": "S3",
      "Folder": "Shared/Finance"
    }
  ]
}

Remarque :

--source remote (and all) requires an authenticated session with access to the solution's target Orchestrator. Failures are logged as warnings per kind; the command returns whatever it was able to fetch.

uip solution resource refresh

Re-scan every project in the solution and sync resource declarations from their bindings_v2.json files. Bindings that are not yet in the solution's resource list are created; bindings that match an existing Orchestrator resource are imported. Run this after editing project bindings to bring the solution manifest back in step.

Arguments

Nom	Requis	Objectif
[solutionPath]	non	Path to the solution directory. Defaults to the current directory.

Exemples

# Refresh the current solution
uip solution resource refresh

# Refresh a specific solution directory
uip solution resource refresh ./solutions/finance

Data shape (--output json)

{
  "Code": "ResourceRefresh",
  "Data": {
    "Created": 2,
    "Imported": 1,
    "Skipped": 5,
    "Warnings": [],
    "Status": "Synced 3 resources (5 already in solution)"
  }
}

Created is the count of brand-new solution resources; Imported is the count of resources matched against Orchestrator; Skipped counts bindings that already had a matching solution entry. Warnings is a list of human-readable notes from the sync (empty on a clean run).

Related commands

• uip solution pack — packaging reads the solution's resource list.
• uip solution deploy — deploy provisions resources on the target tenant.
• uip resource — the standalone server-side CRUD tool (different command, different purpose).

Voir également

• Global options — --output, --output-filter, --log-level, --log-file.
• Exit codes — standard exit-code contract.