Closed mdgreenwald closed 1 year ago
@bryantbiggs Have you been able to reproduce this bug?
@bryantbiggs Sorry to be persistent, but I am still seeing this issue in my configuration despite trying to find a workaround.
I have not - the code provided is not deployable unfortunately
I get this issue as well, it feels like it could be related to this issue somehow. Will write back if I find anything.
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
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.
Description
Each time I run
terraform apply
I see a new block in the output:This forces my task to be replaced even if there are no other changes. I also am not able to workaround this issue by adding this block to my configuration.
I am not able to share the complete configuration in this issue report, however I could send it via other means if required.
⚠️ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Reproduction Code [Required]
Steps to reproduce the behavior:
terraform apply
terraform plan
ORterraform apply
No
Yes ✅
N/A
Expected behavior
I expect to see no changes immediately after applying and when I have not made any changes to the configuration.
Actual behavior
After applying and making no changes I see forced replacement on the service/task resource.
Terminal Output Screenshot(s)
Additional context