-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ECS service resource always shows difference #2722
Comments
Changing the
|
Thanks for the report. I guess we just need something similar to this: TBH I never referenced IAM roles via names, always via ARNs (I did not know it's even possible). It would be worth checking other IAM-related resources and how these handle the same case. |
To clarify, the IAM role was referenced by its Cool, we can take a stab at the fix and send a PR, I thought it would be straightforward, just wanted to make sure that there was an issue for it. |
Seeing the opposite problem - I've updated a task definition, which is depended on by an ECS service - LMK if I should open a separate issue. |
@rgabo Just noticed your other question:
It does detect it, if you use the right attributes. I'm not sure whether you're using
|
Passing IAM role name into |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
An ECS service defined in Terraform will always include a modify step in the plan because the name of the
iam_role
and the name of thetask_definition
:It seems that the revision of the task definition is included in the original name. Terraform should detect a change in the dependent
task_definition
resource and only modify if necessary.Also, the fully-qualified
iam_role
is compared to the short name of theiam_role
. This can probably be fixed if theaws_iam_role
resource has anarn
output attribute.The text was updated successfully, but these errors were encountered: