Comments (5)
Kind of confusing but I believe this is working as intended as shown here: hashicorp/terraform@fa9758e
Well, working as "intended" may not be working as designed... so this may still be a bug. @catsby @stack72: what do you think here? Should diff suppression be ignored when the default value is used?
from terraform-plugin-sdk.
This is still happening in terraform 0.11.10
Terraform itself handles this well, i.e. when a provider defines a resource which has an attribute foo
with a default value and the diff function set, calling d.get("foo")
in the provider correctly returns the default value when a resource does not specify the foo
attribute.
However, the terraform provider acceptance test framework doesn't behave the same way: the default value for the attribute is ignored and the default value for the type is returned instead.
So I believe ti's a bug in the testing framework...
It would be great to get this fixed as it makes testing providers quite difficult in some cases.
I will have a look to see if I can identify where the change should be made and what it should be, but any pointers would be appreciated.
from terraform-plugin-sdk.
Just wanted to add that, if my understanding of the work-around is correct, it will only work with types such as TypeString or TypeInt, i.e. types that can have at least 3 values: one for the type's default, one for an arbitrary attribute default that helps determine whether or not the user has specified a value for the attribute, and one for the actual value of the attribute as specified by the user.
It then means that the work-around does not actually work for attributes of type TypeBool.
So imho, this bug prevents providers with attributes of type TypeBool defining a default value and a suppress func to be succesfully acceptance tested.
from terraform-plugin-sdk.
Hi folks 👋
A lot has changed with Terraform CLI and terraform-plugin-sdk between when this issue was raised and now. For example, there have been significant updates to the difference handling logic and the acceptance testing framework now uses real Terraform CLI commands and artifacts rather than re-implementing or emulating some of the previous Terraform core logic internally. State value checking should be wholly representative of an actual terraform apply
.
If you are still running into problems in this area with recent versions of Terraform CLI and the SDK, my suggestion would be to open a new issue so we can take a fresh look. Thanks so much.
from terraform-plugin-sdk.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
from terraform-plugin-sdk.
Related Issues (20)
- `diff.GetOk` return `nil` for the value of `TypeList` defined in `TypeSet` HOT 1
- Not Helpful Err When Running Tests For Provider HOT 4
- Unsupported Field Type for Resource
- TypeSet resource wanting to destroy and recreate everything when diff is found HOT 2
- losing precision when using maximum value for a 64-bit signed integer
- helper/schema: Provide Functionality to Reduce Resident Memory Usage from Schemas HOT 1
- Consider Method for Disabling Legacy SDK Data Consistency Warning Log Demotion HOT 7
- Updates for Protocol Version 5.4 HOT 1
- Value out of range on 32-bit architecture HOT 3
- Update Go Module to Go 1.20 Minimum HOT 1
- `Schema.Set` adds an empty value when attempting to Patch HOT 1
- `meta.SDKVersion` reporting incorrect version HOT 6
- Terraform CloudFormation Multi Region Stacksets HOT 3
- Is it possible to have a dependency between 2 attributes? HOT 2
- `schema.ResourceData.GetRaw<whatever>()` not populated during provider configuration HOT 3
- Consider Migrating from mitchellh/mapstructure to go-viper/mapstructure
- Low performance in deduplicate strings function HOT 4
- ForceNew doesn't trigger resource recreation when defined on TypeSet, which leads to Update error HOT 1
- helper/resource: Add Go Deprecation Messages That Point To terraform-plugin-testing
- Don't print `UnexpectedStateError.LastError` when it's nil
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-plugin-sdk.