docs: Custom SAN examples

[pandirigoog]

Description

Fixes #

Note: If you are not associated with Google, open an issue for discussion before submitting a pull request.

Checklist

Readiness

• Yes, merge this PR after it is approved
• No, don't merge this PR after it is approved

Style

• My sample follows the rules described for Terraform in the Effective Samples style guide
• My sample follows the other requirements and best practices in the Contributing
  guide

Testing

• I have performed tests described in the Contributing guide:

  • Tests pass: terraform apply
  • Lint pass: terraform fmt check

Intended location

• Yes, this sample will be (or already is) included on cloud.google.com
  Location(s):

• No, this sample won't be included on cloud.google.com
  Reason:

API enablement

• If the sample needs an API enabled to pass testing, I have added the service to the Test setup file

Review

• If this sample adds a new directory, I have added codeowners to the CODEOWNERS file

[snippet-bot]

Here is the summary of changes.

You are about to add 18 region tags.

• cloud_sql/mysql_instance_custom_subject_alternative_names/main.tf:16, tag cloud_sql_mysql_instance_service_identity
• cloud_sql/mysql_instance_custom_subject_alternative_names/main.tf:23, tag cloud_sql_mysql_privateca_ca_pool_suffix
• cloud_sql/mysql_instance_custom_subject_alternative_names/main.tf:31, tag cloud_sql_mysql_instance_ca_pool
• cloud_sql/mysql_instance_custom_subject_alternative_names/main.tf:43, tag cloud_sql_mysql_instance_ca
• cloud_sql/mysql_instance_custom_subject_alternative_names/main.tf:82, tag cloud_sql_mysql_instance_iam_granting
• cloud_sql/mysql_instance_custom_subject_alternative_names/main.tf:91, tag cloud_sql_mysql_instance_custom_subject_alternative_names
• cloud_sql/postgres_instance_custom_subject_alternative_names/main.tf:16, tag cloud_sql_postgres_instance_service_identity
• cloud_sql/postgres_instance_custom_subject_alternative_names/main.tf:23, tag cloud_sql_postgres_privateca_ca_pool_suffix
• cloud_sql/postgres_instance_custom_subject_alternative_names/main.tf:31, tag cloud_sql_postgres_instance_ca_pool
• cloud_sql/postgres_instance_custom_subject_alternative_names/main.tf:43, tag cloud_sql_postgres_instance_ca
• cloud_sql/postgres_instance_custom_subject_alternative_names/main.tf:82, tag cloud_sql_postgres_instance_iam_granting
• cloud_sql/postgres_instance_custom_subject_alternative_names/main.tf:91, tag cloud_sql_postgres_instance_custom_subject_alternative_names
• cloud_sql/sqlserver_instance_custom_subject_alternative_names/main.tf:16, tag cloud_sql_sqlserver_instance_service_identity
• cloud_sql/sqlserver_instance_custom_subject_alternative_names/main.tf:23, tag cloud_sql_sqlserver_privateca_ca_pool_suffix
• cloud_sql/sqlserver_instance_custom_subject_alternative_names/main.tf:31, tag cloud_sql_sqlserver_instance_ca_pool
• cloud_sql/sqlserver_instance_custom_subject_alternative_names/main.tf:43, tag cloud_sql_sqlserver_instance_ca
• cloud_sql/sqlserver_instance_custom_subject_alternative_names/main.tf:82, tag cloud_sql_sqlserver_instance_iam_granting
• cloud_sql/sqlserver_instance_custom_subject_alternative_names/main.tf:91, tag cloud_sql_sqlserver_instance_custom_subject_alternative_names

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[msampathkumar]

PR has a great start! Need minor changes to improve.

1. Try to keep region tags unique
2. Add descriptions or comments to understand why a resources is created. This optional for your but very helpful for me & users to understand your motivation.

Example: description = "Create example sql instance with CA ..."

[msampathkumar]

LGTM!