Good morning everyone, so in an attempt of better ...
# all-things-deployment
m
Good morning everyone, so in an attempt of better understanding the guts of Datahub, I have encountered with some env variables that don't know what they are used for but they have to be created. Some examples of said variables would be
DATAHUB_APP_VERSION
,
DATAHUB_SECRET
,
DATAHUB_SYSTEM_CLIENT_SECRET
, .... I have been trying to look in the site of the project, but haven't been lucky. Any help would be apreciated!
a
i believe the client id and secret are used by services to auth themselves with the backend (gms). The frontend and some of the other components use it for this purpose i think.
m
Thanks @average-vr-23088 for the answer. Do you know if there is any official documentation of it? Or you just know it by experience and deduction?
a
Not really much docs on those in particular, it was more just from deduction while i was setting things up. There is a personal access token which serves as a way to auth with GMS as well, for programmatic use. The Client ID and secret from what i’ve seen in the code (the datahub actions container in particular) is used almost like a system level auth. For example, you can make requests to GMS with basic auth using the client_id:client_secret.