Update the deployment.toml configuration to match the keystore created

[HasiniSama]

Purpose

$subject

This will ensure a smooth user experience when changing the hostname. The current values given are not in par with sample command about creating the keystore.

Summary by CodeRabbit

• Documentation
  • Updated keystore configuration documentation with new sample values for both JKS and PKCS12 keystore format examples.
  • Added comprehensive TOML configuration block format documentation for the keystore.primary section, providing detailed specifications and field references for file names, authentication passwords, certificate aliases, key passwords, and keystore type configuration options.

[coderabbitai]

Walkthrough

Documentation update introducing a formal TOML configuration format specification for keystore.primary and updating sample configuration values for JKS and PKCS12 keystores with simplified, consistent naming conventions.

Changes

Cohort / File(s)	Summary
Keystore Configuration Documentation en/includes/deploy/change-the-hostname.md	Added TOML "Format" block defining keystore.primary configuration fields (file_name, password, alias, key_password, type). Updated JKS and PKCS12 sample entries: simplified file names (e.g., "new-keystore.jks" → "newkeystore.jks"), standardized passwords and aliases across formats (→ "mypassword", "newcert").

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Documentation-only change with no logic modifications
• Repetitive, consistent pattern updates across keystore format examples
• Straightforward value replacements with minimal surface area for errors

Suggested reviewers

• Lakshan-Banneheke
• himeshsiriwardana
• ShanChathusanda93

Poem

🐰 A keystore tale I now shall tell,
Where format blocks and samples dwell!
New names arise, so clean and bright,
Configuration shines just right—
Newcert and mypassword take their flight! 🔐

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides purpose and context with supporting screenshots, but lacks required sections: Related PRs, Test environment, and Security checks from the template.	Complete the description by adding the missing template sections: Related PRs, Test environment details, and Security checks with checkboxes marked appropriately.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly describes the main change: updating deployment.toml configuration values to align with keystore creation samples, which matches the PR's core objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 008e509 and 3b63301.

📒 Files selected for processing (1)

• en/includes/deploy/change-the-hostname.md (1 hunks)

🔇 Additional comments (3)

en/includes/deploy/change-the-hostname.md (3)

68-77: Well-structured documentation format section.

The new Format block clearly shows the generic TOML configuration structure for keystore.primary using consistent placeholder notation (<keystore_name>, <keystore_password>, etc.), which aligns with the pattern used throughout the document.

---

79-88: Sample values now align with keytool command at line 27.

The JKS configuration sample now uses consistent values (newkeystore.jks, newcert, mypassword) that directly correspond to the keytool command shown earlier, making it straightforward for users to apply the same values in their deployment configuration.

---

90-99: Sample values align consistently with PKCS12 keytool command at line 33.

The PKCS12 configuration sample now mirrors the JKS pattern with matching values (newkeystore.p12, newcert, mypassword), ensuring consistency across both keystore formats and making the documentation easier to follow end-to-end.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[HasiniSama]

The lint failures are irrelevant to this change.