provider: adding a unit test covering the design of the encryption block
#20462
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…block marked as Computed These should instead be marked as `Computed: false` and use delta/patch updates - allowing users to use `ignore_changes` across the Provider whilst there's a subset of resources which support this today - these have been temporarily excluded to allow this to be fixed in 4.0
This'll make this obvious when we look to enable the feature-flags
|
This functionality has been released in v3.44.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a mostly consistent implementation of
encryptionblocks across new resources - where the presence of theencryptionblock means that a customer managed key should be enabled (with required fields inside of it) - and the omission of the block meaning that the service provided key should be used instead.There's a handful of both data sources and resources which don't match these rules, to avoid this test failing these have been explicitly allowed to fail until v4.0 - but this should prevent new data sources/resources, or new functionality within existing ones from being added to the provider.