Add Cloud WAF Instance response computed properties #77
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.
Enhancement to add Cloud WAF Instance read response computed properties for:
removed as duplicate tocloudwaf_instance_id
- This maps to the API responseid
property. The name has been modified for Terraform asid
is not an allowed field name. The error isid is a reserved field name for a resource
. See more here:id
is now a reserved field name in Terraform russellcardullo/terraform-provider-pingdom#11id
value.deployment
- This maps to thedeployment
API response property. While this is a JSON object in the API response, this is currently implemented asschema.TypeList
withMaxItems
set to1
instead of being aschema.TypeMap
due to a limitation in the Terraform Provider Go SDK which requiresschema.TypeMap
values to be strings. Using aTypeList
wil result in deterministic 0-based hash indexes, so a property can be retrieved asdeployment.0.dns_entry
. This limitation conflicts with implementingdeployment.egressIPs
which is an array of object. See more here: Add support for maps with non-primitive types (rich / object map support) hashicorp/terraform-plugin-sdk#62