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

Added a new datasource for fetching the available alloydb locations #7678

Merged
merged 60 commits into from
Apr 19, 2023

Conversation

ravisiddhu
Copy link
Contributor

@ravisiddhu ravisiddhu commented Apr 10, 2023

This PR is for hashicorp/terraform-provider-google#13812

A new datasource google_alloydb_locations for fetching the details of available alloydb locations. It receives project as arguments and returns the details of all the available alloydb locations.

I have added documentation and tested this new data source with unit tests.

If this PR is for Terraform, I acknowledge that I have:

  • Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes).
  • Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests).
  • Generated Terraform providers, and ran make test and make lint in the generated providers to ensure it passes unit and linter tests.
  • Ran relevant acceptance tests using my own Google Cloud project and credentials (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).
  • Read the Release Notes Guide before writing my release note below.
`google_alloydb_locations`

ravisiddhu and others added 30 commits December 5, 2022 17:44
… user from setting "password" or "host" for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT user types.
… or password field for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT
@modular-magician
Copy link
Collaborator

Tests passed during RECORDING mode:
TestAccDataSourceGoogleFirebaseAndroidAppConfig[Debug log]
TestAccBigtableAppProfile_bigtableAppProfileAnyclusterExample[Debug log]
TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example[Debug log]
TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample[Debug log]
TestAccDataSourceAlloydbLocations_basic[Debug log]

All tests passed
View the build log or the debug log for each test

@rileykarson
Copy link
Member

rileykarson commented Apr 12, 2023

Adding @NickElliot as initial reviewer (@zli82016 will do final review and merge afterwards)

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 4 files changed, 254 insertions(+))
Terraform Beta: Diff ( 4 files changed, 254 insertions(+))
TF Conversion: Diff ( 2 files changed, 3 insertions(+), 3 deletions(-))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2631
Passed tests 2348
Skipped tests: 277
Affected tests: 6

Action taken

Found 6 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
TestAccDataSourceGoogleFirebaseAndroidAppConfig|TestAccDataSourceAlloydbLocations_basic|TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example|TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample|TestAccAlloydbCluster_missingLocation|TestAccAlloydbBackup_missingLocation

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

Tests passed during RECORDING mode:
TestAccDataSourceGoogleFirebaseAndroidAppConfig[Debug log]
TestAccDataSourceAlloydbLocations_basic[Debug log]
TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example[Debug log]
TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample[Debug log]
TestAccAlloydbCluster_missingLocation[Debug log]
TestAccAlloydbBackup_missingLocation[Debug log]

All tests passed
View the build log or the debug log for each test

@NickElliot
Copy link
Contributor

LGTM! @zli82016 for final review

}

url, err := ReplaceVars(d, config, "{{AlloydbBasePath}}projects/{{project}}/locations")
log.Printf("[ERROR] kanthara url : %s", url)
Copy link
Member

@zli82016 zli82016 Apr 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this log required? Or is it just for your local development? You can remove it if it is not needed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ravisiddhu , can you please remove this line? After that, I will merge the PR.

Copy link
Contributor Author

@ravisiddhu ravisiddhu Apr 19, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zli82016, It is not needed, I have removed it.

@zli82016
Copy link
Member

Overall LTGM.

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 4 files changed, 252 insertions(+))
Terraform Beta: Diff ( 4 files changed, 252 insertions(+))
TF Conversion: Diff ( 2 files changed, 3 insertions(+), 3 deletions(-))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2630
Passed tests 2346
Skipped tests: 277
Affected tests: 7

Action taken

Found 7 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
TestAccAlloydbBackup_missingLocation|TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample|TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example|TestAccAlloydbCluster_missingLocation|TestAccDataSourceGoogleFirebaseAndroidAppConfig|TestAccDataSourceAlloydbLocations_basic|TestAccTPUNode_tpuNodeFullExample

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

Tests passed during RECORDING mode:
TestAccAlloydbBackup_missingLocation[Debug log]
TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample[Debug log]
TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example[Debug log]
TestAccAlloydbCluster_missingLocation[Debug log]
TestAccDataSourceGoogleFirebaseAndroidAppConfig[Debug log]
TestAccDataSourceAlloydbLocations_basic[Debug log]
TestAccTPUNode_tpuNodeFullExample[Debug log]

All tests passed
View the build log or the debug log for each test

@zli82016 zli82016 merged commit afd6cf3 into GoogleCloudPlatform:main Apr 19, 2023
ravisiddhu added a commit to ravisiddhu/magic-modules that referenced this pull request Apr 25, 2023
…oogleCloudPlatform#7678)

* Added validation for "type" in cloud_sql_user_resource for preventing user from setting "password" or "host" for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT user types.

* Removed validation and added documentation to prevent setting of host or password field for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT

* Added a new data source for fetching the details of available alloydb locations

* using go client libraries to call the apis

* using go client library to call the apis

* using go client library to call the apis

* Using v1 and v1beta go client for ga and beta versions respectively

* Using v1 and v1beta go client for ga and beta versions respectively

* Revert "Added a new data source for fetching the details of available alloydb locations"

This reverts commit a6791a3.

* calling http calls using magic modules send request insted of alloydb go client

* calling http calls using magic modules send request insted of alloydb go client
maphad pushed a commit to maphad/magic-modules that referenced this pull request Apr 27, 2023
…oogleCloudPlatform#7678)

* Added validation for "type" in cloud_sql_user_resource for preventing user from setting "password" or "host" for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT user types.

* Removed validation and added documentation to prevent setting of host or password field for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT

* Added a new data source for fetching the details of available alloydb locations

* using go client libraries to call the apis

* using go client library to call the apis

* using go client library to call the apis

* Using v1 and v1beta go client for ga and beta versions respectively

* Using v1 and v1beta go client for ga and beta versions respectively

* Revert "Added a new data source for fetching the details of available alloydb locations"

This reverts commit a6791a3.

* calling http calls using magic modules send request insted of alloydb go client

* calling http calls using magic modules send request insted of alloydb go client
maphad pushed a commit to maphad/magic-modules that referenced this pull request Apr 27, 2023
…oogleCloudPlatform#7678)

* Added validation for "type" in cloud_sql_user_resource for preventing user from setting "password" or "host" for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT user types.

* Removed validation and added documentation to prevent setting of host or password field for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT

* Added a new data source for fetching the details of available alloydb locations

* using go client libraries to call the apis

* using go client library to call the apis

* using go client library to call the apis

* Using v1 and v1beta go client for ga and beta versions respectively

* Using v1 and v1beta go client for ga and beta versions respectively

* Revert "Added a new data source for fetching the details of available alloydb locations"

This reverts commit a6791a3.

* calling http calls using magic modules send request insted of alloydb go client

* calling http calls using magic modules send request insted of alloydb go client
maphad pushed a commit to maphad/magic-modules that referenced this pull request Apr 27, 2023
…oogleCloudPlatform#7678)

* Added validation for "type" in cloud_sql_user_resource for preventing user from setting "password" or "host" for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT user types.

* Removed validation and added documentation to prevent setting of host or password field for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT

* Added a new data source for fetching the details of available alloydb locations

* using go client libraries to call the apis

* using go client library to call the apis

* using go client library to call the apis

* Using v1 and v1beta go client for ga and beta versions respectively

* Using v1 and v1beta go client for ga and beta versions respectively

* Revert "Added a new data source for fetching the details of available alloydb locations"

This reverts commit a6791a3.

* calling http calls using magic modules send request insted of alloydb go client

* calling http calls using magic modules send request insted of alloydb go client
ericayyliu pushed a commit to ericayyliu/magic-modules that referenced this pull request Jul 26, 2023
…oogleCloudPlatform#7678)

* Added validation for "type" in cloud_sql_user_resource for preventing user from setting "password" or "host" for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT user types.

* Removed validation and added documentation to prevent setting of host or password field for CLOUD_IAM_USER and CLOUD_IAM_SERVICE_ACCOUNT

* Added a new data source for fetching the details of available alloydb locations

* using go client libraries to call the apis

* using go client library to call the apis

* using go client library to call the apis

* Using v1 and v1beta go client for ga and beta versions respectively

* Using v1 and v1beta go client for ga and beta versions respectively

* Revert "Added a new data source for fetching the details of available alloydb locations"

This reverts commit a6791a3.

* calling http calls using magic modules send request insted of alloydb go client

* calling http calls using magic modules send request insted of alloydb go client
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants