-
-
Notifications
You must be signed in to change notification settings - Fork 355
task_definition version always known after apply #72
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
Comments
Having the same issue |
Same issue present in my deployments as well. |
I have same issue. I seem that this issue is caused by this PR. |
@antonbabenko |
Using a data provider prevents terraform converging forcing an update on every apply. It doesn't have the data available since it's pulling from AWS when it has it locally already. https://www.terraform.io/docs/configuration/data-sources.html#data-resource-dependencies
Using a data provider prevents terraform converging forcing an update on every apply. It doesn't have the data available since it's pulling from AWS when it has it locally already. https://www.terraform.io/docs/configuration/data-sources.html#data-resource-dependencies
Fix issue #72 task_definition known after apply Using a data provider prevents terraform converging. Basically until the apply runs it doesn't have the data to know which revision is great. Forcing it to be updated on every apply. It doesn't have the data available since it's pulling from AWS when it has it locally already. It does mean if you update the task_definition in the AWS console this will overwrite it. Which I believe is correct behaviour. e.g. I bumped the task_definition manually to 16 and it will roll it back.
https://www.terraform.io/docs/configuration/data-sources.html#data-resource-dependencies |
Using a data provider means terraform doesn't have the information required until runtime to determine if the `task_definition` needs to be updated. Subsequently an update is triggered on every `apply`. It has the information locally already, by removing the indirection of a data provider terraform can correctly reconcile if any updates are required prior to `apply` being run. Essentially it's making the dependency between the `aws_ecs_service` and `aws_ecs_task_definition` explicit rather than implied through the `data` provider and `depends_on` https://www.terraform.io/docs/configuration/data-sources.html#data-resource-dependencies Currently atlantis shows an update everytime a plan or apply is run despite o configuration changes. terraform-aws-modules#72 None that I'm aware of. - Confirmed that updating the vars that are used in the `task_definition` trigger an update - Manually create a new task_definition revision and confirm that terraform will role back to the AWS, plan/apply and manual changes
does anyone have a workaround for this issue? |
…m-aws-modules#72) A data lookup for the latest task definition revision to be used in the ECS service was enabled by default, which continually appeared in plans/applies. This is used when the task definition's updated by an external deployment tool, so this is now disabled and requires enabling the `external_task_definition_updates` variable so the default behaviour is quiet.
…m-aws-modules#72) A data lookup for the latest task definition revision to be used in the ECS service was enabled by default, which continually appeared in plans/applies. This is used when the task definition's updated by an external deployment tool, so this is now disabled and requires enabling the `external_task_definition_updates` variable so the default behaviour is quiet.
I have the same issue. i think
|
Looks like this was fixed in #163 |
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. |
Hello,
While using this module, I get the following message every time I do
terraform apply
.Is there any way to avoid this?
The following is my module usage:
The text was updated successfully, but these errors were encountered: