We do not seem to be able to manage Environment Variables via git. Is there something we can configure to make this possible?
They also seem to reside outside of the versions which suggests that if one developer makes a change to an Environment Variable while he/she has switched to their own development version of a project then this could effect the work of another dev working in another version.
The fact they are not committed to git also means deploying to a prod version requires the Env Variables to be manually updated as an additional step.
I think the theory is that the default values of variables are likely to 1) be relatively static and 2) need to vary between Development and Production. So they are deliberately maintained separately from all Job logic.
Or a more prosaic answer is that git basically manages Project/Exports, and Project/Exports don't contain variable values - for the same reasons. If you look in the JSON from a Matillion export, it contains the names of variables but not any values.
You are correct in that environment variables are not included as part of the Git integration. There are a few objects like this that you will find don't end up in Git when you do a commit. The current Git integration is pretty rudimentary but Matillion is actively working on a solution to make this a bit more complete and robust. We use the Git integration but don't put a lot of value in it as there are other ways to manage source. We are anxiously waiting for the updates that Matillion is working on. 🙂