github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-05-06 08:55:40 -05:00
Code Issues 3.5k Packages Projects Releases 103 Wiki Activity

[GH-ISSUE #189] [Feature] Parsed compose config preview #3152

New Issue
Open
opened 2026-04-13 14:48:21 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 14:48:21 -05:00
Owner
Copy Link

Originally created by @em411 on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/moghtech/komodo/issues/189

Description

Currently, Komodo's UI displays the raw content of compose.yaml files without processing Docker Compose's advanced features. This makes it difficult to understand the actual configuration that will be used during deployment, especially when using features like:

Usage

To improve user experience and provide better visibility of the actual configuration, we should integrate the equivalent of docker compose config command output in the UI, which shows the fully parsed and resolved configuration.

Use Case

Makes it easier to audit and debug configuration issues by showing the complete resolved state.

Originally created by @em411 on GitHub (Nov 15, 2024). Original GitHub issue: https://github.com/moghtech/komodo/issues/189 # Description Currently, Komodo's UI displays the raw content of `compose.yaml` files without processing Docker Compose's advanced features. This makes it difficult to understand the actual configuration that will be used during deployment, especially when using features like: - [Merge](https://docs.docker.com/compose/how-tos/multiple-compose-files/merge/) - [Extend](https://docs.docker.com/compose/how-tos/multiple-compose-files/extends/) - [Include](https://docs.docker.com/compose/how-tos/multiple-compose-files/include/) - [Fragments](https://docs.docker.com/reference/compose-file/fragments/) - [Extensions](https://docs.docker.com/reference/compose-file/fragments/) - [Interpolation](https://docs.docker.com/reference/compose-file/interpolation/) - [Profiles](https://docs.docker.com/reference/compose-file/profiles/) # Usage To improve user experience and provide better visibility of the actual configuration, we should integrate the equivalent of `docker compose config` command output in the UI, which shows the fully parsed and resolved configuration. # Use Case Makes it easier to audit and debug configuration issues by showing the complete resolved state.
GiteaMirror added the enhancement label 2026-04-13 14:48:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
2.0.0
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
v2
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#3152
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?