Skip to content
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

Remove IP validation for host of on-premise instance #16235

Conversation

modular-magician
Copy link
Collaborator

According to API doc to setup a source representation instance, user can pass the IPv4 address and port for the external server, or the the DNS address for the external server. When user try to pass DNS address in terraform configuration file, they encounter Error: could not parse "host" to IP address.

In admin API, we don't have validation for host of on-premise instances. As of now it is validating that host contain the IP address in terraform. In order to be consistent with admin API and accept DNS address as well, removing the validation function for host.

Release Note Template for Downstream PRs (will be copied)

sql: removed host validation to support IP address and DNS address in host in `google_sql_source_representation_instance` resource

Derived from GoogleCloudPlatform/magic-modules#9225

* Remove IP validation for host of on-premise instance

In admin API, we don't have validation for host of on-premise instances. Host can take the value of IP address or DNS address. As of now it is validating that host contain the IP address in terraform, in order to be consistent with admin API and accept DNS address as well, removing the validation function for host.

* Update the description of the host field
[upstream:e8667f2683131ffa0b14914d9e4821c1ad6a43f6]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit 4110683 into hashicorp:main Oct 12, 2023
4 checks passed
Copy link

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 issues.
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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant