feat: add recursive discovery of compose files up to 10 levels #1268
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature allows podman-compose to locate a compose file (e.g., docker-compose.yml, compose.yml, etc.) when executed from deep within a project structure.
If a user runs
podman-compose ps
from a subdirectory likeproject/addons/module/component
, the tool will search upward through parent directories (up to 10 levels) to find a compose file located in the root of the project (e.g.,project/
).This improves usability by eliminating the need to manually navigate to the project root or specify the
--file
option.Notes:
docker-compose.yml
,compose.yml
Contributor Checklist:
If this PR adds a new feature that improves compatibility with docker-compose, please add a link
to the exact part of compose spec that the PR touches.
For any user-visible change please add a release note to newsfragments directory, e.g.
newsfragments/my_feature.feature. See newsfragments/README.md for more details.
All changes require additional unit tests.