-
Notifications
You must be signed in to change notification settings - Fork 121
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
kendra_index getting replaced on failed kendra_faq re-deployment #1562
Comments
This is happening with Steps to reproduce:
|
I believe the problem with Kendra FAQ is upstream AWS.
thanks for reporting this, we'll investigate this separately. |
From inspecting the execution plan, there's one particular attribute (
|
Could you please share your Terraform state file for resource |
likely relates to #1139 |
It is.
|
On my recent test with provider AWSCC Terraform plan is no longer triggering replacement, I believe thanks to the fix on #1712, however it still detecting drift
Debug log is telling interesting story:
Attribute in question: |
The remaining problem in this issue is now more relevant to problem discussed in #1216. Further debug logs: PlanResourceChange_Request_PriorState
PlanResourceChange_Request_ProposedNewState Notice the attribute
|
@quixoticmonk , the original issue (force replacement) has been resolved, I would like to continue the discussion on the remaining issue at #1795 to keep the discussion separate. As such, I am going to go ahead and close this issue. |
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Terraform plan
Steps to Reproduce
terraform apply
terraform apply
with the changes to original failed FAQ ( CSV to CSV_CSV_WITH_HEADER)Important Factoids
References
The text was updated successfully, but these errors were encountered: