DXE-3463 Bug: Rule builder does not generate the correct default value for the customCertificate property

[antoine-savignac-nm]

When there is no custom certificates, the provider should generate the rule JSON with a default value of [] for the custom_certificate property in the origin rule.

Terraform Version

1.2.5

Rule format

rules_v2023_10_30

Provider version

5.5.0

Affected Resource(s)

• akamai_property_rules_builder

Terraform Configuration Files

behavior {
      origin {
        cache_key_hostname = "REQUEST_HOST_HEADER"
        compress           = true
        custom_certificate_authorities {
          ...
        }

        custom_certificate_authorities {
          ...
        }
        custom_valid_cn_values = [
          "{{Origin Hostname}}",
          "{{Forward Host Header}}"
        ]
        enable_true_client_ip            = true
        forward_host_header              = "REQUEST_HOST_HEADER"
        hostname                         = var.origin_hostname
        http_port                        = 80
        https_port                       = 443
        origin_certificate               = ""
        origin_certs_to_honor            = "COMBO"
        origin_sni                       = true
        origin_type                      = "CUSTOMER"
        ports                            = ""
        standard_certificate_authorities = ["akamai-permissive"]
        true_client_ip_client_setting    = false
        true_client_ip_header            = "True-Client-IP"
        verification_mode                = "CUSTOM"
      }
    }

Expected Behavior

The "origin" rule should have been created and added to the property without custom certificates
"customCertificates": [],

Actual Behavior

The API call to activate the property failed because the rule configuration is wrong.
API Error message:

15:57:07 │ Error: activation cannot continue due to rule errors: [
15:57:07 │ 	{
15:57:07 │ 		"behavior_name": "",
15:57:07 │ 		"detail": "The Specific Certificates (pinning) option on the `Origin Server` behavior is required.",
15:57:07 │ 		"error_location": "#/rules/behaviors/0/options/customCertificates",
15:57:07 │ 		"instance": "",
15:57:07 │ 		"status_code": 0,
15:57:07 │ 		"title": "",
15:57:07 │ 		"type": "https://problems.luna.akamaiapis.net/papi/v0/validation/attribute_required"
15:57:07 │ 	}
15:57:07 │ ]

Steps to Reproduce

1. terraform apply

Important Factoids

If you try to add an empty block (in the HCL) you get an empty object inside a list (in the JSON output), example:
Input:

custom_certificate { }

Output:

{
  "customCertificates": [{}],
}

And this fails when we try to activate the property because it doesn't match the schema

16:40:26 │ 	"title": "Input does not match schema",
16:40:26 │ 	"detail": "Your input has a syntax problem.  Please double check against the schema.",

References

[lsadlon]

Hello @antoine-savignac-nm

Thank you for raising this issue. We were able to reproduce it and create internal ticket to fix it.

BR,
Lukasz

[lkowalsk-akamai-com]

This issue should be fixed with recent release.