-
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 being being forced replaced without any changes to the resource definition #1795
Comments
thanks for the reply @quixoticmonk, I will wait until you have tested it on your side too
But the issue is still happening for me: So for now I will just wait and see if you are able to validate the fix since I might be doing something wrong on my side, cheers |
I think this is very similar to issue discussed here |
@acbsn , thank you for reporting this issue. At the surface, it might looked like the problem was due to Debug log is telling interesting story, the actual attribute in question is
|
relates to #1216 |
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
We have integrated terraform with Gitlab, so we are using the gitlab's latest stable docker image:
Provider:
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Running
terraform plan
without any changes to the kendra index definition should not force replace the resource.Actual Behavior
After deploying the kendra index, running plan again always displays:
causing the index to be deleted and recreated.
I tried explicitly adding a null configuration for the kms key, but it did not work.
And I also tried adding a lifecycle policy, but it also did not work,
Steps to Reproduce
Important Factoids
References
This issue might be related to: #1562
The text was updated successfully, but these errors were encountered: