uip maestro bpmn update-metadata

Syntax and options for the deprecated `uip maestro bpmn update-metadata` command — use `uip maestro bpmn refresh` instead.

警告:

Deprecated. Use uip maestro bpmn refresh instead. The command still works and is documented below for existing scripts, but every invocation prints a [WARN] deprecation notice to stderr.

uip maestro bpmn update-metadata writes (or checks) project.uiproj, operate.json, entry-points.json, bindings_v2.json, and package-descriptor.json from a .bpmn file. Unlike refresh, it does not materialize Integration Service connection bindings — a package produced this way is not guaranteed runnable. It's registered under the bpmn branch.

概要

uip maestro bpmn update-metadata <bpmn> [--output-dir <dir>] [--dry-run]

グローバルオプションを優先します。終了コードは 標準コントラクトに従います。

引数

• <bpmn> (必須) — .bpmn ファイルのパスです。

オプション

オプション	既定 (Default)	説明
--output-dir <dir>	directory of <bpmn>	Directory for the metadata JSON files. In --dry-run mode, this is the directory whose existing files are checked for drift instead.
--dry-run	無効	Report drift against the .bpmn file without writing anything.

例

# Write metadata files next to the .bpmn
uip maestro bpmn update-metadata process.bpmn

# Check for drift without writing
uip maestro bpmn update-metadata process.bpmn --dry-run

データシェイプ(--output json)

Write mode:

{
  "Code": "MaestroBpmnUpdateMetadata",
  "Data": {
    "DryRun": false,
    "ProjectName": "process",
    "OutDir": "/workspace/my-project",
    "FilesWritten": [
      "project.uiproj",
      "operate.json",
      "entry-points.json",
      "bindings_v2.json",
      "package-descriptor.json"
    ],
    "EntryPointCount": 1
  }
}

--dry-run mode:

{
  "Code": "MaestroBpmnUpdateMetadata",
  "Data": {
    "DryRun": true,
    "Status": "OK",
    "Drifts": []
  }
}

参照

• uip maestro bpmn refresh — current replacement, also materializes Integration Service connection bindings
• uip maestro bpmn init — scaffold a new project instead of hand-assembling metadata
• Maestro の概要