Use environment-based Docker image in Docker-compose

[jnsereko]

The idea here is to use Hashicorp Vault and direnv to automate env secrets.

The ideology is simple

• Install and setup Hashicorp Vault and direnv locally
• go to the home directory of this repo and run direnv allow . ( otherwise direnv will not load the env files)
• we shall have a simple private script to run once, which will set secrete data ie, database user, password, name etc
• we first load the secrets in the envrc using direnv
• run direnv source_env .env.dev for dev environment or direnv source_env .env.qa for the qa environment
• finally do our usual docker compose up

I am open for further discussion on this
cc @michaelbontyes

[sherrif10]

You got failures on this repo @jnsereko

[jnsereko]

You got failures on this repo @jnsereko

Upload Configuration Artifact should fail. Looking into Build and Validate Configuration

[jnsereko]

closing this because i have a better approach
I will reopen when this approach turns out better

[jnsereko]

uncertified logic in this is when we have different secretes for both qa and dev

Solution:
Creating different variables for secretes ie having QA_OPENMRS_DB_USER and DEV_OPENMRS_DB_USER and dynamically loading these variable in the docker compose file

[sherrif10]

Makes sense, In that case you can manage different configs for different variables.