-
Notifications
You must be signed in to change notification settings - Fork 473
fix: replace invalid optional(string, ) with optional(string) #725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: replace invalid optional(string, ) with optional(string) #725
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
@steamedEggMaster thx for the PR. can u plz sign CLA? |
|
@imrannayer I’ve signed the CLA. Let me know if anything else is needed. Thanks! |
|
waiting on fix #726 merge |
|
/gcbrun |
3 similar comments
|
/gcbrun |
|
/gcbrun |
|
/gcbrun |
|
/gcbrun |
1 similar comment
|
/gcbrun |
056e436
into
terraform-google-modules:main
What
Replaced all instances of
optional(string, )withoptional(string, null)across thepostgresqlandmysqlmodules.Why
While the syntax
optional(string, )does not currently cause errors in Terraform and works as expected, it is not officially valid HCL. The presence of the trailing comma can cause confusion for contributors or users reading the code, especially those unfamiliar with how Terraform interprets it.This change aims to improve clarity and avoid potential misunderstandings, without introducing any functional changes.
Testing
All modules passed validation:
terraform init && terraform validate