feat: rename binary to pgedge-control-plane

[jason-lynch]

Summary

Renames the binary from control-plane to pgedge-control-plane to reduce the chance of conflicts with other packages.

Testing

Dev builds and dist artifacts should continue to work as normal.

PLAT-417

[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: 5dc02345-98d4-4555-9afc-ec382f239e47

📥 Commits

Reviewing files that changed from the base of the PR and between 40fd983 and ab652f8.

📒 Files selected for processing (10)

• .gitignore
• .goreleaser.yaml
• Makefile
• docker/control-plane-ci/Dockerfile
• docker/control-plane-dev/Dockerfile
• docker/control-plane-dev/docker-compose.yaml
• docker/control-plane-dev/entrypoint.sh
• docker/control-plane/Dockerfile
• docs/development/running-locally.md
• e2e/fixtures/roles/build_image/vars/main.yaml

✅ Files skipped from review due to trivial changes (9)

• .gitignore
• docker/control-plane-dev/Dockerfile
• docker/control-plane-dev/docker-compose.yaml
• docs/development/running-locally.md
• docker/control-plane-ci/Dockerfile
• .goreleaser.yaml
• e2e/fixtures/roles/build_image/vars/main.yaml
• docker/control-plane/Dockerfile
• docker/control-plane-dev/entrypoint.sh

---

📝 Walkthrough

Walkthrough

The control-plane executable name was changed project-wide from control-plane to pgedge-control-plane, updating build outputs, release packaging, Docker images/entrypoints, dev compose/watch paths, docs, and archive naming.

Changes

Cohort / File(s)	Summary
Ignore rules \.gitignore	Added pgedge-control-plane to ignore patterns while keeping existing exceptions (e.g., !docker/control-plane).
Release / Build config \.goreleaser.yaml, Makefile	Renamed project/binary from control-plane → pgedge-control-plane for goreleaser and Makefile build/release targets and artifact paths.
Docker: CI image docker/control-plane-ci/Dockerfile	COPY and ENTRYPOINT updated to use /pgedge-control-plane instead of /control-plane.
Docker: Dev image & compose docker/control-plane-dev/Dockerfile, docker/control-plane-dev/docker-compose.yaml, docker/control-plane-dev/entrypoint.sh	Build copy, host watch/sync paths, and entrypoint execution updated to pgedge-control-plane (both debug and normal modes).
Docker: Release image docker/control-plane/Dockerfile	Archive extraction name and ENTRYPOINT updated to reference pgedge-control-plane.
Documentation docs/development/running-locally.md	All user-facing instructions and examples updated to reference pgedge-control-plane instead of control-plane.
E2E fixture / archive naming e2e/fixtures/roles/build_image/vars/main.yaml	Template _archive_name changed to prefix archives with pgedge- producing pgedge-control-plane_{{ version }}_...tar.gz.

Poem

🐇 I hopped through builds and Docker lanes,
Renamed my coat and changed my gains,
From control-plane to pgedge I prance,
A tiny binary on a big new dance,
Burrito of bytes — a joyous chance! 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete according to the repository template, missing the Changes section (bulleted list), Testing commands, and most of the Checklist items required for PRs.	Add a Changes section with bullet points listing the files modified, provide specific testing commands (e.g., 'make dev-build', 'make goreleaser-build'), and complete the Checklist with details about tests, docs, and changelog entries.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: renaming the binary from 'control-plane' to 'pgedge-control-plane', which aligns with the comprehensive changes across all configuration and Docker files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/PLAT-417/rename-binary

---

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

[jason-lynch]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

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.

[rshoemaker]

Looks good. I think there are some usages in here that need s/control-plane/pgedge-control-plane/

https://github.com/pgEdge/control-plane/blob/feat/PLAT-417/rename-binary/docs/development/running-locally.md?plain=1

Lines 199, 202, & 205.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

📝 Walkthrough

Walkthrough

The control-plane executable is being renamed from control-plane to pgedge-control-plane across build configurations, container images, and deployment scripts. This includes updates to build outputs, Dockerfile references, and runtime paths.

Changes

Cohort / File(s)	Summary
Build Configuration .gitignore, .goreleaser.yaml, Makefile	Added pgedge-control-plane to ignore patterns and updated build artifact naming to reflect the new executable name across release packaging and development build targets.
CI Docker Configuration docker/control-plane-ci/Dockerfile	Updated COPY instruction and ENTRYPOINT to reference the renamed binary pgedge-control-plane instead of control-plane.
Dev Docker Configuration docker/control-plane-dev/Dockerfile, docker/control-plane-dev/docker-compose.yaml, docker/control-plane-dev/entrypoint.sh	Updated container build instructions, file-watch sync paths, and entrypoint script to use the renamed pgedge-control-plane binary in both DEBUG and standard execution modes.
Release Docker Configuration docker/control-plane/Dockerfile	Updated ENTRYPOINT to invoke /pgedge-control-plane instead of /control-plane.

Poem

🐇 Our binary hops to a brand new name,
From control-plane to pgedge-control-plane it came,
Through Dockerfiles, compiles, and build-time flame,
A rebranding journey, perfectly tame! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is incomplete. While it includes a Summary section explaining the purpose and Testing section describing expected outcomes, it lacks the Changes, Checklist, and Notes for Reviewers sections required by the template.	Add the missing sections: provide a bulleted list of high-level changes, complete the pre-merge checklist, and include notes for reviewers if applicable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: rename binary to pgedge-control-plane' directly and clearly summarizes the main change across all modified files—renaming the binary artifact throughout the build, deployment, and execution configurations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/PLAT-417/rename-binary

---

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