Terraform Provider Does Not Support Hyphen in Custom Properties Configuration

[leij-splunk]

Description:
The current version of the Terraform provider exhibits a limitation by not supporting hyphens in Custom Properties configuration. This deviation poses an inconsistency with the expected behavior and functionality.

Additional Information:

• Terraform Provider Version: v2.0.3
• Relevant Code Snippet:
  

  terraform-provider-synthetics/synthetics/resource_api_check_v2.go

  Line 205 in cd66308

  ValidateFunc: validation.StringMatch(regexp.MustCompile(`^[a-zA-Z]\w{1,128}$`), "custom_properties key must start with a letter and only consist of alphanumeric and underscore characters with no whitespace"),

  
  

  terraform-provider-synthetics/synthetics/resource_api_check_v2.go

  Line 210 in cd66308

  ValidateFunc: validation.StringMatch(regexp.MustCompile(`^\w{1,256}$`), "custom_properties value can only consist of alphanumeric and underscore characters with no whitespace"),

• Custom properties Document:
  • Key Requirements:
    • Must start with a letter.
    • Allowed characters include letters, numbers, underscores, and hyphens.
    • Naming restrictions: Can't be named test_id or test.
    • Character limit: Key size cannot exceed 128 characters.
  • Value Requirements:
    • Allowed characters include letters, numbers, underscores, and hyphens.

[greatestusername-splunk]

Thanks for adding this issue! Will double check the regex with the backend and if other chars are allowed update the validate function!

[bambro]

@greatestusername-splunk can you confirm the requirements of the property values? Hyphens and other special characters are allowed in the UI however are excluded by terraform

[greatestusername-splunk]

@bambro
These should work in terraform now. Latest version included an updated regex for allowing hyphens and underscores.

[greatestusername-splunk]

Closing as #44 should address this issue in full. If it does not please re-open another issue.

Thanks!