add force_update field to kubernetes_manifest schema

[BBBmau]

Description

kubernetes_manifest would now give users the option to override the destroy and recreate action with just a replacement in cases where a value in CRD is marked as x-kubernetes-preserve-unknown-fields

It should be documented that this field should only be turned on in very specific use cases since DynamicTypes can cause some issues.

Fixes #2371
Fixes #2375
Fixes #1928

Acceptance tests

• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch?

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

Release Note

Release note for CHANGELOG:

...

References

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[BBBmau]

Let me know your thoughts on this @alexsomesan

[BBBmau]

closing this since a more robust method for dealing with the listed issues is in the works.

[RafalKorepta]

Hi, @BBBmau What you mean by

more robust method for dealing with the listed issues is in the works

I'm interested in exactly your proposal to have option to output from the recreation process. Is there any PR or GH issue that I could follow? Maybe you expect any dates when such feature could land?

Thank you and whole Hashicorp team for trying to merit terraform with Kubernetes :)