-
Notifications
You must be signed in to change notification settings - Fork 21
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
Timestamp changes cause plan output to force change #22
Comments
I see the same using a Kibana/ES 8 cluster it looks like the following attributes are going to change everytime, so they should be excluded
edit: |
Hum, it's strange, because of
|
Maybee you can try with verison v8.5.1 |
@disaster37 thanks for the update..
is ignored as expected but is shown in the change log if there is another change.. maybe it would be cool to document this and also add an example like this
|
After creating a Kibana object, the rule is successfully created. However, when you re-run terraform plan, it detects a change every time, because /api/saved_objects/_import automatically updates timestamps (such as updated_at).
The text was updated successfully, but these errors were encountered: