docs: systemd docs recommend enterprise repo download

[GabriellePoncey]

Summary

Recommend installing and updating the Control Plane package on systemd hosts from the pgEdge Enterprise dnf/apt repositories,since the control-plane package will begin publishing there starting with the next release. The existing GitHub Releases curl-based method is kept as a fallback for air-gapped hosts or pinning an exact version.

Changes

• Installing the Control Plane doc now recommends dnf install/apt install pgedge-control-plane from the enterprise repo, keeps original logic as a fallback subsection.
• docs/installation/systemd-upgrading.md: same treatment for upgrades, enterprise repo recommended but fallback kept

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 47275814-0a82-4c1e-bf76-2d32eca47276

📥 Commits

Reviewing files that changed from the base of the PR and between df0b4c6 and e3c5515.

📒 Files selected for processing (2)

• docs/installation/systemd-installation.md
• docs/installation/systemd-upgrading.md

🚧 Files skipped from review as they are similar to previous changes (2)

• docs/installation/systemd-upgrading.md
• docs/installation/systemd-installation.md

---

📝 Walkthrough

Walkthrough

The systemd installation and upgrade guides now recommend Enterprise repository workflows, document RPM and Debian commands, clarify architectures and installed paths, and organize GitHub release instructions into nested package subsections.

Changes

Systemd package documentation

Layer / File(s)	Summary
Systemd installation guidance docs/installation/systemd-installation.md	Documents supported architectures, installed paths, Enterprise repository and GitHub installation commands, and removes duplicated Debian installation instructions.
Systemd upgrade guidance docs/installation/systemd-upgrading.md	Adds Enterprise repository upgrade commands and restructures the GitHub release package subsections.

Poem

A rabbit hops through docs so neat,
With package paths beneath its feet.
RPM carrots, Debian greens,
GitHub trails in tidy scenes.
Upgrade burrows now align—
“Install!” squeaks Bun, “and upgrade fine!”

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes Summary and Changes, but it omits the required Testing, Checklist, and Notes for Reviewers sections.	Add the missing Testing, Checklist, and Notes for Reviewers sections, and note any linked issue, changelog entry, or breaking changes if applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the docs-focused change and clearly points to the new enterprise repo recommendation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/PLAT-659/install-repo-enterprise

---

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.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/installation/systemd-installation.md`:
- Around line 95-98: Update the opening installation description in the systemd
installation documentation to present the configured pgEdge Enterprise package
repositories as the primary installation method, with GitHub Releases explicitly
described as the fallback for users without repository access.
- Around line 118-121: Clarify the air-gapped workflow in the installation
documentation: instruct users to download the package from the GitHub releases
page on an internet-connected machine and transfer it to the air-gapped host
before installation, or remove the air-gapped example if that workflow is not
supported.

In `@docs/installation/systemd-upgrading.md`:
- Line 14: Insert an h2 parent heading before the existing “RPM Package” heading
in the upgrade methods section, such as “Updating from Enterprise Repositories,”
so the RPM and Debian headings remain properly nested without changing their
content.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0d44dc15-5aed-4dcb-be0d-2142437a04bb

📥 Commits

Reviewing files that changed from the base of the PR and between b082b80 and df0b4c6.

📒 Files selected for processing (2)

• docs/installation/systemd-installation.md
• docs/installation/systemd-upgrading.md

[GabriellePoncey]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.