[-] The provider becomes dependent to the server's implementation, which potentially means more work to support all existing flavors and versions.
[-] The encryption is performed by the implementation which come with additional responsibility (e.g. not forgetting to encrypt any attribute with sensitive information) (more tests required)
[-] The provider has to stay aligned with the official CLI and applications, in order for items encrypted by one tool to be decryptable by another tool. This means, encrypting the same fields for example.
The idea would be to release the feature as experimental first, until the test coverage is extended and people got the opportunity to report problems and concerns.
Add a Bitwarden client as part of the project (see https://github.com/maxlaverse/terraform-provider-bitwarden/issues/26)
It's still experimental, but would offer the similar trade-off:
The idea would be to release the feature as experimental first, until the test coverage is extended and people got the opportunity to report problems and concerns.