Pattern question regarding environments

[davideagle]

Hi and thank you for publishing this pattern. I'm wondering how you handle and prevent environment drifts in this pattern. From what I gather (please correct if wrong) you'd have separate directory structure in the ESM (environment service module) for each environment (dev/test/stage/prod) would that not create a lot of code duplications and create a possibility for environment drifts as you changes some things in one environment and but not the other?

I'd like to hear your thought on this since in my opinion it should preferably be the same code that is used to create each env to ensure as close similarity between them as possible.

[jonbrouse]

Hey sorry for the delay. Using trunk based development, only the "dev" environment would be on the master branch. When you're ready to deploy to QA, Stage, etc. you would either use a tag or a commit hash. This allows you to keep your service modules in step with the code base it is deploying. Does that answer your question?