DUPLO-26299 Build fix

[duplodavid]

User description

Describe Changes

Build fix by removing any potential cyclic dependencies in docker-compose.yaml.

Link to Issues

DUPLO-26299

Related: docker/compose 12235

---

PR Type

enhancement, documentation

---

Description

• Removed potential cyclic dependencies in docker-compose.yaml by explicitly defining inherited sections.
• Updated docker-compose.yaml to include specific image tags and build arguments.
• Added environment variables for the duploctl-bin service.
• Updated CHANGELOG.md to reflect the changes made in the docker-compose.yaml.

---

Changes walkthrough 📝

	Relevant files
Documentation	CHANGELOG.md Update changelog with cyclic dependency fix                            CHANGELOG.md Added an entry about removing potential cyclic dependencies in docker-compose.yaml. +1/-0
Enhancement	docker-compose.yaml Fix cyclic dependencies and update service configurations docker-compose.yaml Removed cyclic dependencies by explicitly defining sections. Updated image tags and build arguments. Added environment variables for duploctl-bin. +16/-4

---

💡 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]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 Security concerns Environment Variable Exposure: The docker-compose file includes environment variables for authentication (DUPLO_TOKEN) and API endpoints (DUPLO_HOST). While they use default empty values, ensure these are properly secured in production and not exposed in logs or container inspection.

⚡ Recommended focus areas for review Version Consistency Multiple image tags are defined but there's no clear strategy for version consistency across services. Validate that the versioning approach aligns with the project's release strategy. Configuration Duplication Environment variables are duplicated between duploctl and duploctl-bin services. Consider using YAML anchors or a shared environment file to maintain DRY principle.

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Explicitly specify the Docker Compose file version to ensure compatibility and prevent potential issues with different Docker versions Consider adding a version field at the top of the docker-compose file to explicitly specify the compose file format version being used. docker-compose.yaml [1-3] +version: '3.8' services: duploctl: &base image: &image duplocloud/duploctl:latest Apply this suggestion Suggestion importance[1-10]: 4 Why: While adding a version field is a good practice for Docker Compose files, it's not critical as modern Docker versions default to latest format. The current file works correctly without it.	4

💡 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: 190053b by action🐍