azurerm_synapse_sql_pool Allow UTF-8 characters in SQL pool name

[owenfarrell]

Signed-off-by: Owen Farrell [email protected]<!--- Please keep this note for the community --->

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Summary

This pull request updates the validation logic associated with Synapse SQL pool names to support UTF-8 characters and other non-alphanumeric characters that are supported by Azure.

Fixes: #11554

Output from acceptance testing:

$ make acctests SERVICE='synapse' TESTARGS='-run=TestAccSynapseSqlPool_utf8' TESTTIMEOUT='30m'
==> Checking that code complies with gofmt requirements...
==> Checking that Custom Timeouts are used...
==> Checking that acceptance test packages are used...
TF_ACC=1 go test -v ./internal/services/synapse -run=TestAccSynapseSqlPool_utf8 -timeout 30m -ldflags="-X=github.com/hashicorp/terraform-provider-azurerm/version.ProviderVersion=acc"
=== RUN   TestAccSynapseSqlPool_utf8
=== PAUSE TestAccSynapseSqlPool_utf8
=== CONT  TestAccSynapseSqlPool_utf8
--- PASS: TestAccSynapseSqlPool_utf8 (980.83s)
PASS
ok      github.com/hashicorp/terraform-provider-azurerm/internal/services/synapse       983.397s

[katbyte]

Thanks @owenfarrell - LGTM 🏗️

[github-actions]

This functionality has been released in v2.76.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.