IF Commons GitHub

merge

verbdestructive

Bring two stores that merge together: a plan first with its hash (what each takes from the other), then the apply that the hash approves; there is no conflict to settle.

Program anyfs-writer. Origin anyfs.

Governance: the action

What the verb is and may do, as governance says it. Each annotation is expressed by the surfaces or says why it is not.

PropertyValue
kindaction
effectdestructive
idempotentfalse
audienceboth
tierwriter
dryRuntrue
checkfalse
reachChannelslocal, mcp
reachReadOnlyfalse
reachNeedsTtyfalse
reachRunsAscaller
reachConfirmationflag

Operands

OperandMeaning
AThe first store that merges.
BThe second store that merges.

Options

OptionMeaningProperties
--max-rowsRefuse a plan in which a store would take more than N rows at once.type=value, required=false, standard=false, humanOnly=false, valueName=N
--max-bytesRefuse a plan in which a store would take more than N bytes of blobs at once.type=value, required=false, standard=false, humanOnly=false, valueName=N
--plan-hashApply only the plan with this hash: where the stores changed since it was read, nothing is applied.type=value, required=false, standard=false, humanOnly=false, valueName=HASH
--trustWhom to take changes from: open (anyone), allowlist (the replicas of --replicas) or signed (the keys of --roster). Where it is left out the mount says, and where the mount says nothing the store keeps the trust it has.type=value, required=false, standard=false, humanOnly=false, valueName=MODE
--rosterThe keys that are known, as a file of a JSON list (or env:NAME, a variable that holds the text): for --trust signed.type=value, required=false, standard=false, humanOnly=false, valueName=FILE
--sign-keyThe keys that sign what is published, each a file (or env:NAME, a variable that holds the key): a delta is signed with the key of the replica that made it. The key is never given on the command line.type=value, required=false, standard=false, humanOnly=false, valueName=FILE[,FILE]
--replicasThe replicas that are taken changes from, by identity (32 hexadecimal digits); with --trust signed it narrows the roster.type=value, required=false, standard=false, humanOnly=false, valueName=ID[,ID]
--jsonWrite one JSON document and nothing else for a person.type=flag, required=false, standard=true, humanOnly=false, negatable=false, default=false
--quietShow only how it ended.type=flag, short=q, required=false, standard=true, humanOnly=false, negatable=false, default=false
--verboseShow every step as it happens.type=flag, short=v, required=false, standard=true, humanOnly=false, negatable=false, default=false
--colorUse colour where the terminal shows it (--no-color turns it off).type=flag, required=false, standard=true, humanOnly=false, negatable=true, default=true
--non-interactiveNever ask a question: where one is needed, fail and say so.type=flag, required=false, standard=true, humanOnly=false, negatable=false, default=false
--dry-runShow what would change and change nothing.type=flag, required=false, standard=true, humanOnly=false, negatable=false, default=false
--yesConfirm the destruction without asking.type=flag, short=y, required=false, standard=true, humanOnly=false, negatable=false, default=false

Examples

anyfs merge --dry-run fleet-a:/ fleet-b:/  # What each store takes from the other, and the hash of that plan; nothing is changed.
anyfs merge --yes --plan-hash <hash> fleet-a:/ fleet-b:/  # Bring them together: each takes what the other has, whole or not at all.

Physical: what it is drawn as

anyfs merge

cli-command. Bring two stores that merge together: a plan first with its hash (what each takes from the other), then the apply that the hash approves; there is no conflict to settle.

PropertyValue
usageanyfs merge
wordsmerge
tierwriter

anyfs_merge

mcp-tool. Bring two stores that merge together: a plan first with its hash (what each takes from the other), then the apply that the hash approves; there is no conflict to settle. (action, effect destructive.)

PropertyValue
titleanyfs merge
toolNameanyfs_merge
readOnlyHintfalse
destructiveHinttrue
idempotentHintfalse
inputsmaxRows, maxBytes, planHash, trust, roster, signKey, replicas, dryRun, A, B
requiredA, B
tierwriter

Not drawn

  • rest: its reach policy does not name the rest channel

Titles, headings, exports, tables, columns and requirements. Esc closes.