Update docker compose for 1.0.0

[BeArchiTek]

• Add missing env variable
• Replace infrahub-git by task-worker
• Get ready to support CACHE_USERNAME and CACHE_PASSWORD (still need to update the cache service itself @fatih-acar

[fatih-acar]

I think we don't need this volume anymore, but I still see it in the development docker-compose...
Can you confirm @dgarros?

I'm asking because we removed it from the Helm chart, and it seems to be still working. If the volume is still required, we'd need to also fix the Helm chart.

[ogenstad]

I realise that we don't have the variables for specific SSO providers.

INFRAHUB_OAUTH2_GOOGLE_ICON
INFRAHUB_OAUTH2_GOOGLE_CLIENT_ID
INFRAHUB_OAUTH2_GOOGLE_CLIENT_SECRET
INFRAHUB_OAUTH2_GOOGLE_AUTHORIZATION_URL
INFRAHUB_OAUTH2_GOOGLE_USERINFO_URL
INFRAHUB_OAUTH2_GOOGLE_SCOPE
INFRAHUB_OAUTH2_GOOGLE_DISPLAY_LABEL
INFRAHUB_OAUTH2_GOOGLE_TOKEN_URL

INFRAHUB_OAUTH2_PROVIDER1_ICON
INFRAHUB_OAUTH2_PROVIDER1_CLIENT_ID
INFRAHUB_OAUTH2_PROVIDER1_CLIENT_SECRET
INFRAHUB_OAUTH2_PROVIDER1_AUTHORIZATION_URL
INFRAHUB_OAUTH2_PROVIDER1_USERINFO_URL
INFRAHUB_OAUTH2_PROVIDER1_SCOPE
INFRAHUB_OAUTH2_PROVIDER1_DISPLAY_LABEL
INFRAHUB_OAUTH2_PROVIDER1_TOKEN_URL

INFRAHUB_OAUTH2_PROVIDER2_ICON
INFRAHUB_OAUTH2_PROVIDER2_CLIENT_ID
INFRAHUB_OAUTH2_PROVIDER2_CLIENT_SECRET
INFRAHUB_OAUTH2_PROVIDER2_AUTHORIZATION_URL
INFRAHUB_OAUTH2_PROVIDER2_USERINFO_URL
INFRAHUB_OAUTH2_PROVIDER2_SCOPE
INFRAHUB_OAUTH2_PROVIDER2_DISPLAY_LABEL
INFRAHUB_OAUTH2_PROVIDER2_TOKEN_URL

INFRAHUB_OIDC_GOOGLE_ICON
INFRAHUB_OIDC_GOOGLE_DISPLAY_LABEL
INFRAHUB_OIDC_GOOGLE_CLIENT_ID
INFRAHUB_OIDC_GOOGLE_CLIENT_SECRET
INFRAHUB_OIDC_GOOGLE_DISCOVERY_URL
INFRAHUB_OIDC_GOOGLE_SCOPE

INFRAHUB_OIDC_PROVIDER1_ICON
INFRAHUB_OIDC_PROVIDER1_DISPLAY_LABEL
INFRAHUB_OIDC_PROVIDER1_CLIENT_ID
INFRAHUB_OIDC_PROVIDER1_CLIENT_SECRET
INFRAHUB_OIDC_PROVIDER1_DISCOVERY_URL
INFRAHUB_OIDC_PROVIDER1_SCOPE

INFRAHUB_OIDC_PROVIDER2_ICON
INFRAHUB_OIDC_PROVIDER2_DISPLAY_LABEL
INFRAHUB_OIDC_PROVIDER2_CLIENT_ID
INFRAHUB_OIDC_PROVIDER2_CLIENT_SECRET
INFRAHUB_OIDC_PROVIDER2_DISCOVERY_URL
INFRAHUB_OIDC_PROVIDER2_SCOPE

Also perhaps unrelated to this PR but is there a reason why we redefine the default values within the docker compose file?

[BeArchiTek]

I realize that we don't have the variables for specific SSO providers.

INFRAHUB_OAUTH2_GOOGLE_ICON
INFRAHUB_OAUTH2_GOOGLE_CLIENT_ID
INFRAHUB_OAUTH2_GOOGLE_CLIENT_SECRET
INFRAHUB_OAUTH2_GOOGLE_AUTHORIZATION_URL
INFRAHUB_OAUTH2_GOOGLE_USERINFO_URL
INFRAHUB_OAUTH2_GOOGLE_SCOPE
INFRAHUB_OAUTH2_GOOGLE_DISPLAY_LABEL
INFRAHUB_OAUTH2_GOOGLE_TOKEN_URL

INFRAHUB_OAUTH2_PROVIDER1_ICON
INFRAHUB_OAUTH2_PROVIDER1_CLIENT_ID
INFRAHUB_OAUTH2_PROVIDER1_CLIENT_SECRET
INFRAHUB_OAUTH2_PROVIDER1_AUTHORIZATION_URL
INFRAHUB_OAUTH2_PROVIDER1_USERINFO_URL
INFRAHUB_OAUTH2_PROVIDER1_SCOPE
INFRAHUB_OAUTH2_PROVIDER1_DISPLAY_LABEL
INFRAHUB_OAUTH2_PROVIDER1_TOKEN_URL

INFRAHUB_OAUTH2_PROVIDER2_ICON
INFRAHUB_OAUTH2_PROVIDER2_CLIENT_ID
INFRAHUB_OAUTH2_PROVIDER2_CLIENT_SECRET
INFRAHUB_OAUTH2_PROVIDER2_AUTHORIZATION_URL
INFRAHUB_OAUTH2_PROVIDER2_USERINFO_URL
INFRAHUB_OAUTH2_PROVIDER2_SCOPE
INFRAHUB_OAUTH2_PROVIDER2_DISPLAY_LABEL
INFRAHUB_OAUTH2_PROVIDER2_TOKEN_URL

INFRAHUB_OIDC_GOOGLE_ICON
INFRAHUB_OIDC_GOOGLE_DISPLAY_LABEL
INFRAHUB_OIDC_GOOGLE_CLIENT_ID
INFRAHUB_OIDC_GOOGLE_CLIENT_SECRET
INFRAHUB_OIDC_GOOGLE_DISCOVERY_URL
INFRAHUB_OIDC_GOOGLE_SCOPE

INFRAHUB_OIDC_PROVIDER1_ICON
INFRAHUB_OIDC_PROVIDER1_DISPLAY_LABEL
INFRAHUB_OIDC_PROVIDER1_CLIENT_ID
INFRAHUB_OIDC_PROVIDER1_CLIENT_SECRET
INFRAHUB_OIDC_PROVIDER1_DISCOVERY_URL
INFRAHUB_OIDC_PROVIDER1_SCOPE

INFRAHUB_OIDC_PROVIDER2_ICON
INFRAHUB_OIDC_PROVIDER2_DISPLAY_LABEL
INFRAHUB_OIDC_PROVIDER2_CLIENT_ID
INFRAHUB_OIDC_PROVIDER2_CLIENT_SECRET
INFRAHUB_OIDC_PROVIDER2_DISCOVERY_URL
INFRAHUB_OIDC_PROVIDER2_SCOPE

Also perhaps unrelated to this PR but is there a reason why we redefine the default values within the docker compose file?

We redefine the default to make it more "visible" for the users to see what they can change and why some data are like this.

Regarding all the SSO PROVIDER Data, I could had all of them but that seem quite a lot to add for empty value on top on the rest.

We could set all of them in another x-infrahub-config-sso section maybe 🤔

[ogenstad]

We redefine the default to make it more "visible" for the users to see what they can change and why some data are like this.

Ok, was thinking that it's mostly just duplicating data. I also want to get back to generating the configuration in the docs in a proper way. Perhaps that's the main issue behind this that the docs on the config are a bit confusing..

Regarding all the SSO PROVIDER Data, I could had all of them but that seem quite a lot to add for empty value on top on the rest.

We could set all of them in another x-infrahub-config-sso section maybe 🤔

Alternatively we just ignore it. I think this Docker file is mostly to get up and running quickly and in a real production environment users would use something else regardless?

[fatih-acar]

We actually redefine default values in order to use them in the dependencies, such as the message broker auth credentials, cache credentials, etc

[BeArchiTek]

We actually redefine default values in order to use them in the dependencies, such as the message broker auth credentials, cache credentials, etc

As well as the address which are localhost in default, instead of the containers name.