Allow 0 value in vcd_nsxt_alb_edgegateway_service_engine_group.reserved_virtual_services
field
#924
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.
Closes #923
Resource
vcd_nsxt_alb_edgegateway_service_engine_group
fieldreserved_virtual_services
hit a problem where it cannot differentiate between0
and empty value. The reason for it is that Terraform SDK has a limitation forschema.TypeInt
value. (more about it).The way to overcome it is to use
schema.TypeString
instead ofschema.TypeInt
. This works because Terraform does not put explicit differences between int and string in HCL. In the code we convert Int <-> string to match this field. Users would not even notice this change directly, because Terraform has weak typing and you can supplyint
value to aTypeString
field (wihout quotes).To avoid setting some arbitrary string value, there is a schema validator
ValidateFunc: IsIntAndAtLeast(0)
.Testing acceptance, binary and upgrade tests with tag
alb
passed