opschain metadata profiles revise
Included from Basic tier
opschain metadata profiles revise <key> [flags]
Revises a profile (MetadataService.UpdateMetadataProfile). Absent flags
preserve the stored halves. A --file definition replaces the profile's
FULL field set and follows the revision semantics: any
field-set change bumps the version; additive revisions (new field,
widened enum) touch nothing; narrowing ones (removed field, removed enum
value) stale-flag existing values — never delete, never auto-migrate — and
may declare per-field value_mapping old→new entries for the explicit
migrate act. Field types never change in place. The core profile's
field set is base-owned and refuses edits; un-adopting (--adopted=false)
removes a profile's fields from effective resolution and predicates
without touching recorded values (the core profile cannot be un-adopted).
-o json / -o yaml emit the revised profile.
Flags
| Flag | Meaning |
|---|---|
-f, --file <path> | A YAML definition whose fields list replaces the full field set (absent: fields preserved). |
--title <text> | Replace the profile title. |
--description <text> | Replace the profile description. |
--adopted true|false | Adopt or un-adopt the profile. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Revised; the output names the new version. |
| 1 | Refused — no metadata-writer determination, a core field-set edit, or an invalid revision (named by the server). |
| 2 | Usage error, including a missing server target. |