You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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. 🤦♂️
@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?
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.
The text was updated successfully, but these errors were encountered: