SLONIK_CLONE_FINISH(7)

πŸ“¦
version 2.2.11 Β· 4 versions
, in debian trixie, ubuntu questing

πŸ’– SLONIK_CLONE_FINISH(7) πŸ’–

okay bestie, pull up a chair, we're talking about slonik_clone_finish(7) β€” part of the Slony-I 2.2.11 Documentation era, and yes she's iconic πŸŽ€


✨ NAME ✨

CLONE FINISH β€” finish the whole cloning-a-node situation. like, the grand finale. the bow on the gift. periodt πŸ’…


✨ SYNOPSIS ✨

clone finish [ id] [ provider]

(she's short, she's sweet, she's got some optional slots to fill 🫢)


✨ DESCRIPTION ✨

So basically, this command finishes cloning a specified node. that's it, that's the vibe.

But lowkey it's doing the important cleanup work: it wraps up everything that SLONIK CLONE PREPARE(7) started, by establishing confirmation data for the new 'clone' β€” and it figures that out based on the status found for the 'provider' node. so the clone gets its confirmation data, sourced from the provider's status. fr fr, no cap. πŸ¦‹


✨ EXAMPLE ✨

clone finish (id = 33, provider = 22);

there she is. id = 33, provider = 22. chef's kiss, ate, no crumbs πŸ‘‘


✨ SLONIK EVENT CONFIRMATION BEHAVIOUR ✨

⚠️ real talk: Slonik does not wait for event confirmations before performing this command. so don't be out here expecting her to sit around and wait for the confirmation text back, because she will not. she's already moved on. main character energy only 😭

✨ VERSION INFORMATION ✨

This command was introduced in Slony-I 2.0. vintage, but make it slay 🌸


kisses, bestie β€” that's the whole page, you got this πŸ’œ

~ with love, Slony-I 2.2.11, dated 19 September 2024 ~ πŸŽ€πŸ¦‹πŸ’…

πŸ“¦ where this page comes from