mu iam-common is overwritten during deploy

Raising on suggestion from Michael Neil on Gitter

During a mu deploy, i create 4 environments from my single environment mu file, in that file i have a custom cf template for the iam-common to add in EFS permissions. Nothing to strange, but when i deploy a service, db, or pipeline, the iam-common is overwritten. Is this by design ? is there a way to stop this ? I guess the simple answer is to include the CF piece into each mu file, but it seems overkill.

Apr 01 '19 12:04 chris-d-edwards

@chris-d-edwards Did you ever find a way around this? I think I may have just hit this -- I have two services / two mu.yml files, one has an ElastiCache extension that extends the iam-common role, but as soon as the second service is deployed it zaps what that extension added. 🤦‍♂️

Jul 20 '19 03:07 karlskidmore

Update on this, I have added my custom CFN into each mu.yml file

Oct 14 '19 10:10 chris-d-edwards

@chris-d-edwards I don't know if this is a daft idea, but maybe worth a try.... When calling mu pass in the --disable-iam flag on all but the first service?

Oct 14 '19 10:10 karlskidmore

@karlskidmore possibly, I am trying to take the generated CFN and then running that separately now, rather than letting mu control the whole process

Oct 14 '19 10:10 chris-d-edwards