Skip to content
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

Module does not pick up on changes made to task_cpu / task_memory made outside of terraform #259

Open
maggie-weber opened this issue Jan 22, 2025 · 0 comments
Labels
bug 🐛 An issue with the system

Comments

@maggie-weber
Copy link

Describe the Bug

If changes are made to the task_cpu or task_memory values outside of terraform, the module does not see those changes and will not attempt to revert them to the values specified in the module definition.

This was observed using 0.76.0 with FARGATE launch type.

Expected Behavior

The module will observe changes made to the configuration of the ECS task definition made outside of Terraform, and will change the values for these fields back to their original values when deployed.

Steps to Reproduce

  • Create a Fargate task using this module.
  • Set task_memory and task_cpu to any appropriate value.
  • Using the AWS console, deploy a new version of the module with task_memory and task_cpu changed to any other values.
  • terraform plan and observe that cpu and memory are not shown
  • Deploy the application and observe that cpu and memory are still the manually set values even though the infrastructure code specifies differently.

Screenshots

No response

Environment

  • OS: WSL
  • OpenTofu
  • Version 0.76.0

Additional Context

No response

@maggie-weber maggie-weber added the bug 🐛 An issue with the system label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An issue with the system
Projects
None yet
Development

No branches or pull requests

1 participant