gable lineage component tags remove - Gable Docs

Remove a tag from one field. Prompts for confirmation unless —yes is passed. Only a tag applied to the field itself can be removed; the removal is recorded as an event rather than erasing the original, so the history stays auditable.

Usage

gable lineage component tags remove [OPTIONS]

Options

Option	Type	Required	Default	Description
`--endpoint`	text			Customer API endpoint for Gable, in the format https://api.company.gable.ai/. Can also be set with the GABLE_API_ENDPOINT environment variable.
`--api-key`	text			API Key for Gable. Can also be set with the GABLE_API_KEY environment variable.
`--component-id`	text	✓		Component UUID. Names are not accepted on writes; find the UUID with `gable lineage component list`.
`--direction`	`ingress`	`egress`	✓		Which side of the component the field is on.
`--xgress`	text	✓		The path carrying the field, addressed by path ID or payload name, as `tags list` prints them.
`--field`	text	✓		The field, e.g. ‘contact.email’.
`--dry-run`	boolean		false	Print the assignment that would be sent without applying it.
`--tag`	text	✓		Tag definition id to remove, e.g. ‘pii’.
`--yes`	boolean		false	Skip the confirmation prompt. Required when running non-interactively.

⌘I