1

As a developer working in team I don't like using CMI to synch config from/into development server at all (cim/cex) in local development machine. Instead I'd like to use Feature. What I wanted to achieve is on below diagram.

enter image description here

Basically I want to use Features for development in first tier and use CMI only for deployment to PRD/IGR. Does it make sense? What do you think?

  • Why not just use CMI for all of it? Would be more consistent. – David Thomas Sep 30 '16 at 11:37
  • @DavidThomas because by using cim/cex you can do mess, btw what the point of ex/im all site config when you are working on certain feature. – Codium Sep 30 '16 at 13:13
  • It's possible to use both Features and CMI, I suppose just use whatever best suits your workflow there. – David Thomas Sep 30 '16 at 13:23
  • Basically I'm looking for more argue positive & negative to have more knowledge to convince rest of the team – Codium Sep 30 '16 at 13:45
1

Some comments according to the limited experience i have on CMI myself.

I believe that what you ask is pretty much logical, due to the fact that local dev envs usually end up being different than the actual remote Dev instance. Testing modules, code, configuration e.t.c is pretty much the reason for that. This makes default CMI functionality unusable as you dont want to move the whole configuration into your actual deployment process (DEV->IGR->PROD).

This problem is addressed quite well using Features, however it could also be tackled by some CMI related modules such as Config partial export or Configuration Split

One more argument in favour of Features might be that you are able to have totally different local dev envs than the remote Dev (Dest site UUID != Source site UUID) which i guess would make CMI unusable.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.