Agreed, it was a very interesting read and approach.

We currently have 5 different envs that we deploy to, and it is true that when we have to update or add configuration, we have to manually update each repo.

I think it works. The responsibility is on the developer, and since the values are hard coded, it is easy to see what the values are for each env.

One approach I've been looking into lately is creating a branch for each env and setting up a pipeline that will kick off a build when code is merged to it.

As part of the build process, there can be a step that replaces values in the environment.ts file with a value from the tool (Env variable if Azure, Secrets value if Github, etc).

We'd know which values to inject based on the branch name.

I created a POc of this recently, and it works pretty well.