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
{{ message }}
This repository has been archived by the owner on Jul 27, 2021. It is now read-only.
This is an FYI for those having the same issue as discussed in mu issue 416
I have been using the current GitHub repos and Mu 1.5.10
During the frontend deployment, when deploying the container to the acceptance environment, there is a consistent error which is demonstrated through an issue with the ECS EC2 and deploying the task.
There are suggestions that this could be a mu issue related to the deploy-cluster policy please see: stelligent/mu#416
However there is an issue with the "new ARN and resource ID format" Opt in; please see: stelligent/mu#414
I have changed my setting to have opted out to the new ARN and resource id's and re run the platform and frontend deployments. This appears to be an answer for now, until the fix for 416 is promoted to a mu release.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is an FYI for those having the same issue as discussed in mu issue 416
I have been using the current GitHub repos and Mu 1.5.10
During the frontend deployment, when deploying the container to the acceptance environment, there is a consistent error which is demonstrated through an issue with the ECS EC2 and deploying the task.
There are suggestions that this could be a mu issue related to the deploy-cluster policy please see:
stelligent/mu#416
However there is an issue with the "new ARN and resource ID format" Opt in; please see: stelligent/mu#414
I have changed my setting to have opted out to the new ARN and resource id's and re run the platform and frontend deployments. This appears to be an answer for now, until the fix for 416 is promoted to a mu release.
The text was updated successfully, but these errors were encountered: