opschain metadata profiles create

Included from Basic tier

opschain metadata profiles create -f <profile.yaml>

Adopts a customer metadata profile from a YAML definition (MetadataService.CreateMetadataProfile). Customer field families must live under x-<org>.* — non-x- families are reserved for the base core vocabulary and pack-shipped bindings. Needs the metadata-writer determination at /.

The strict YAML vocabulary:

key: x-acme-ops
title: Acme operations vocabulary
description: ...
fields:
  - key: x-acme.tier          # <family>.<field>
    type: enum                # string|enum|bool|integer|duration|date|node_ref|external_ref
    enum_values: [gold, silver]
    applies_to: asset         # project|environment|asset|any
    inherit: none             # none|subtree
    protective: false
    required: false
    description: ...

-o json / -o yaml emit the created profile.

Flags

Flag	Meaning
-f, --file <path>	The YAML profile definition (mandatory).

Exit codes

Code	Meaning
0	Created.
1	Refused — no metadata-writer determination, a reserved key, or an invalid field spec (named by the server).
2	Usage error — a missing/unparseable file, an unknown YAML key, or a missing server target.