orke package save
Save the task definition against the observed saved revision.
When to use it
Save the task definition against the observed saved revision.
Usage
Syntax · [ ] marks optional arguments
orke package save --slug <string> --text <string> --expectedRevision <string> [--force <boolean>]Options
| Options | Required? | Value and description |
|---|---|---|
--slug | Required | Package identifier returned by list or create. |
--text | Required | Original text to enter or save. |
--expectedRevision | Required | Definition revision read with get. |
--force | Optional | Choice for resolving a save conflict after reviewing the current contents. |
Common management options and errors →
Example
Terminal
orke package save --slug package_slug --text "Contents to save" --expectedRevision revision_from_getReplace the example IDs, folders, references, and revision with values from actual queries. Element references such as e7 must also come from the latest observation.
What to check in the result
PackageDescriptor: definition/revision/readError, runtime/target/allowedActions, completedStages/attention/recovery
Behavior and states to watch
- Save the definition using the observed revision. During a run, changes apply from the next cycle. text/stdin must be raw strict UTF-8, up to 1048576 bytes.
- Use either text or --stdin. The raw text must be strict UTF-8, up to 1,048,576 bytes. Empty text, whitespace, and line breaks are preserved.