DUPLO-26299 Rename duploctl Directive to duploctl-base

[duplodavid]

User description

Describe Changes

Rename duploctl Directive to duploctl-base to fix build issue.

Link to Issues

DUPLO-26299

Related: docker/compose 12235

---

PR Type

enhancement

---

Description

• Renamed the duploctl directive to duploctl-base across multiple configuration files to address a build issue.
• Updated the GitHub Actions workflow to use the new target name.
• Modified VSCode tasks to reflect the new directive name.
• Updated the Docker Compose configuration to rename the service.
• Revised the contributing guide to include the updated build command.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	image.yml Rename build target in GitHub Actions workflow                      .github/workflows/image.yml Renamed build target from duploctl to duploctl-base. +1/-1      tasks.json Update VSCode tasks to new directive name                                .vscode/tasks.json Updated task arguments to use duploctl-base instead of duploctl. +1/-1      docker-compose.yaml Rename service in Docker Compose configuration                      docker-compose.yaml Renamed service from duploctl to duploctl-base. +1/-1
Documentation	CONTRIBUTING.md Update contributing guide with new build command                  CONTRIBUTING.md Changed build command example to use duploctl-base. +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[zafarabbas]

Task linked: DUPLO-26299 duploctl build issue

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit ec17f93)

Action: Image

Failed stage: Build and Push Docker Image [❌]

Failure summary: The action failed due to a configuration error in the Docker setup: A cycle was detected in the Docker Compose file at the path services.duploctl-bin.build.args. This indicates a circular dependency or reference within the Docker Compose configuration, which prevents successful processing.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 802: IMAGE: duplocloud/duploctl 803: REPO: duploctl 804: GIT_SHA: ec17f93 805: GIT_REF: DUPLO-26299-build-issue 806: ##[endgroup] 807: #1 [internal] load local bake definitions 808: #1 reading docker-compose.yaml 1.04kB / 1.04kB done 809: #1 DONE 0.0s 810: ERROR: cycle detected at path: services.duploctl-bin.build.args 811: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Naming Consistency Verify that renaming the service from 'duploctl' to 'duploctl-base' doesn't break any dependent services or configurations that might reference the original service name

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Maintain naming consistency between service name and Docker image name Update the image name in the image anchor to match the new base name for consistency with the service rename. docker-compose.yaml [4] -image: &image duplocloud/duploctl:latest +image: &image duplocloud/duploctl-base:latest Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion correctly identifies the need to maintain consistency between the service name (duploctl-base) and the Docker image name. This alignment is important for clarity and maintainability of the Docker configuration.	7

💡 Need additional feedback ? start a PR chat

[duploctl]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
2217	442	20%	0%	🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: ec17f93 by action🐍