Skip to content

REL-1368082: Add configure-retention CLI command user guide for Environment Watch - #77

Open
amithshet wants to merge 4 commits into
mainfrom
REL-1368082-cli-configure-retention-doc
Open

REL-1368082: Add configure-retention CLI command user guide for Environment Watch#77
amithshet wants to merge 4 commits into
mainfrom
REL-1368082-cli-configure-retention-doc

Conversation

@amithshet

Copy link
Copy Markdown
Collaborator

Summary

Adds a user guide for the \configure-retention\ Relativity Server CLI command, following the same structure and conventions as the
otate-api-key\ guide (PR #69).

The \configure-retention\ command was implemented in relativityone/server-relativity-environmentwatch#570 and shipped in version 102.1.26.

Terminal output examples have been verified against actual CLI output from a test VM.

Files changed

  • New: \�lastic-stack-setup/elastic-stack-setup-02-environment-watch/elastic-stack-configure-retention-environment-watch.md\

    • Overview and prerequisites
    • Options table (--logs-days, --metrics-days, --traces-days, --quiet, --dryrun)
    • Usage with verified terminal output: interactive, interactive with pre-filled default, quiet/unattended, dry run (quiet + interactive)
    • Verify section — Kibana Dev Tools \GET /_ilm/policy/infrawatch--policy\
  • Modified: \�lastic-stack-setup/elastic-stack-setup-02-environment-watch/elastic-stack-setup-02-environment-watch.md\

    • Added ## Managing ILM Retention\ cross-reference section before Next Steps

Jira

REL-1368082

@anujavinash
anujavinash self-requested a review August 31, 2026 07:30
@vamsiatluri555

Copy link
Copy Markdown

@amithshet
What happens if the user doesn't change anything? If someone runs the command and just skips past all the prompts without entering any new values, does the tool still show the summary screen and ask "Apply changes? yes/no". even though nothing would actually change?
Also, The guide only documents the happy path (successful update) and one user-initiated cancellation ("Operation cancelled."). It does not cover what the CLI outputs when something goes wrong at runtime such as elasticsearch cluster is unreachable or times out during the update or in similar scenarios?

Covers the review questions on PR #77 and aligns terminal output with the
CLI behaviour captured on the test VM:

- Document what happens when all prompts are skipped: no summary block and
  no confirmation gate, just "Operation cancelled."
- Add Secret Store credential handling for both modes - interactive prompts
  for cluster URL, username and password; quiet mode exits with an error
- Clarify that a first run reports each signal as "not set" rather than
  failing the current-state fetch
- Correct the confirmation prompts to "[y/n] (n)" to match the CLI and the
  rotate-api-key guide
- Replace the vague Elasticsearch prerequisite with a concrete endpoint check
- Remove the troubleshooting section and unverified failure scenarios

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

@vamsiatluri555 vamsiatluri555 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Approved

…y page

Per review feedback on PR #77, consolidates the automated (CLI) and manual
retention configuration guidance onto a single page instead of two:

- Fold the configure-retention CLI content into
  ew-extensibility-configuration-03-retention-policy.md as a new
  "Configure Elasticsearch ILM Retention using the Relativity Server CLI"
  section, replacing the old manual "Configuration Steps" (Kibana Dev Tools
  component-template/index-template edits and destructive data stream
  deletion)
- Delete the now-redundant standalone
  elastic-stack-configure-retention-environment-watch.md
- Repoint the "Managing ILM Retention" link in
  elastic-stack-setup-02-environment-watch.md to the merged section
- Fix a stale link display name in the post-install verification guide

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.

4 participants