Closed johannges closed 4 weeks ago
👌
Hello @johannges ,
Unfortunately there is not much that be done to ameliorate the situation with the current implementation. This is a limitation of the original SDK which this provider still uses. It is something that may be addressable with the new framework which supports more powerful types (which Terraform can track and diff properly). Moving this provider to the new framework is something we are trying to prioritize.
Description
At the moment the diff of the values is unusable. If there is any sensitive information inside one of the strings of the values array, the values are obscured completely. Even otherwise it will just print the complete old and new values.
My suggested solution is to introduce an optional calculated field for a better diff:
Additional field use_computed_values (bool, default_false) Additional field computed_values(optional, calculated):
Potential Terraform Configuration
Potential Terraform Code Change:
References
Community Note