:bug: [BUG]: Load order of `EXTRA_CONF_DIRS` not respected by `COMPOSE_CONF_LIST` about birdhouse-deploy HOT 2 CLOSED

My bad, I did not see this loader order problem in my previous review of #296

For context, the load order is important by design because it allows for the override capabilities describe here

Each org private config, which is suggested to be the last component in the list, should be able to override all previous docker-compose fragments, all previous default.env values and all previous pre/post docker-compose-up scripts.

This component override capabilities, together with env.local, are basically the customization feature allowing each org to change any default behaviors.

from birdhouse-deploy.

@fmigneault I've put up a PR with a fix for the load order issue.

I am unable to replicate the issue regarding the missing ./optional-components/canarie-api-full-monitoring/docker-compose-extra.yml file. That file loads fine when I test it out on my local test environment. I'm using the same EXTRA_CONF_DIRS variable that you have above and the code is currently on the master branch. If that continues to be a problem my guess is that it is unrelated to the load order issue.

The load order is not random, the docker-compose-extra.yml file defined at the root of each component's directory is loaded first. Once all of these are loaded, any overrides that are defined in config/*/docker-compose-extra.yml are loaded.

from birdhouse-deploy.