Skip to content

docs(deploy): two-phase deploy_component, revert_component, stage/activate CLI (draft)#599

Draft
dawsontoth wants to merge 2 commits into
mainfrom
claude/two-phase-deploy-docs
Draft

docs(deploy): two-phase deploy_component, revert_component, stage/activate CLI (draft)#599
dawsontoth wants to merge 2 commits into
mainfrom
claude/two-phase-deploy-docs

Conversation

@dawsontoth

Copy link
Copy Markdown
Contributor

Draft. Documentation companion to the two-phase deploy work in HarperFast/harper#1849 (also a draft). Tracks that PR — the API surface there is still settling (the ops fold landed; the team is finalizing before de-draft), so hold merge until #1849 lands and pin the version badges to the shipping release.

What this documents

The deploy_component operation now runs as a two-phase, cluster-wide deploy, and there are new operator-facing knobs plus a rollback operation. This PR updates the reference docs to match.

reference/operations-api/operations.md

  • deploy_component — documents the internal stage → cluster-wide barrier → activate flow (all-or-nothing at go-live), and the new properties:
    • activate: false — stage-and-stop; returns a staged deployment_id, nothing goes live.
    • deployment_id — activate a previously-staged deployment (no re-fetch/install).
    • revert_on_failure, two_phase, ignore_replication_errors, deployment_timeout.
    • Worked examples for a normal deploy and for stage-now / activate-later.
  • revert_component (new section) — fast cluster-wide rollback to the retained previous version; bidirectional; customer-driven-rollback use case.
  • Deployment lifecycle — updated phase names (stage/activate, legacy prepare/replicate), the new statuses (staging/staged/activating/rolled_back), and staged-build retention (deployment_stagingRetention_maxCount, default 5) with the "aged-out deployment_id" caveat.

reference/cli/operations-api-commands.md

  • Added harper stage, harper activate, and harper revert to the alias table and the aliases list, with examples in Component Operations.

Notes for review

  • Version badges use v5.2.0 as a placeholder — confirm against the actual shipping release before merge.
  • I did not touch the reference_versioned_docs/version-v4/ copies (this is a v5 feature).
  • No new config-reference page was added for deployment_stagingRetention_maxCount; it's described inline where deployments are documented, matching how deployment_payloadRetention_maxSize is currently surfaced. If you'd prefer a dedicated configuration entry, happy to add one.

🤖 Generated with Claude Code

…ivate CLI

Document the two-phase deploy behavior and the new surface from HarperFast/harper#1849:

- deploy_component: cluster-wide stage -> barrier -> activate; new properties
  activate:false (stage-and-stop, returns a staged deployment_id), deployment_id
  (activate a previously-staged deployment), revert_on_failure, two_phase, and
  the ignore_replication_errors / deployment_timeout knobs.
- revert_component: fast cluster-wide rollback to the retained previous version.
- Deployment lifecycle: stage/activate phase names, staged/staging/activating/
  rolled_back statuses, and staged-build retention (deployment_stagingRetention_maxCount).
- CLI: harper stage / activate / revert verbs (aliases + examples).

Companion to HarperFast/harper#1849 (still a draft).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for the CLI and Operations API to reflect the new two-phase deployment process (staging and activation) and the rollback mechanism (revert_component). It introduces new CLI commands, aliases, API parameters, and examples. The review feedback suggests improving consistency by pointing the new CLI operation category links to the main #components section, and enhancing readability in the API documentation by adding clear labels to the multi-step "Stage now, activate later" JSON examples.

Comment thread reference/cli/operations-api-commands.md Outdated
Comment thread reference/operations-api/operations.md
@github-actions
github-actions Bot temporarily deployed to pr-599 July 21, 2026 14:32 Inactive
@github-actions

Copy link
Copy Markdown

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-599

This preview will update automatically when you push new commits.

…tage/activate example

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-599

This preview will update automatically when you push new commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant