Fix getLocalEnvironment failing on older versions of compose without ConfigFiles #681
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.
Older versions of
docker compose
don't have aConfigFiles
key when runningdocker compose ls
. I installed docker compose v2.2.3 from January and this key isn't yet available.It's ideal to use this value directly if it exists, but if it doesn't, we fall back to manually searching the
LOCAL_DEPLOY_PATH
directory and matching the files there up with the results ofdocker compose ls
(which still gives us the name of the compose file).Tested this on my Windows machine that has the older version of docker compose installed, and tested on my Mac that has the most up to date Docker, so the old path is working as it did prior and the new path now fixes the bug.
Bug in question is https://sentry.io/organizations/architect-io/issues/3493163125/?project=6465948&referrer=slack