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

Introduce google_firestore_field resource. #7853

Merged
merged 3 commits into from
May 5, 2023

Conversation

pcostell
Copy link
Contributor

@pcostell pcostell commented May 1, 2023

Introduces a single resource for managing Firestore fields, matching the REST API.

Introduces 2 primary divergences from the proto/REST API:

  1. Firestore fields do not support deletion (this is because all fields
    implicitly can exist in a schemaless system). Deletion of a terraform
    resource will clear any "overrides" for this field (TTL or indexing).
  2. Single field indexes in the proto API were overly nested to allow
    reusing the same resource for composite indexes. The terraform
    resource unnests the 1-length field in the indexes list.

fixes hashicorp/terraform-provider-google#12151
fixes hashicorp/terraform-provider-google#11419
fixes hashicorp/terraform-provider-google#7593

Tested with make testacc TEST=./google TESTARGS='-run=TestAccFirestoreField'

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.

Release Note Template for Downstream PRs (will be copied)

`google_firestore_field`

@modular-magician
Copy link
Collaborator

Hello! I am a robot who works on Magic Modules PRs.

I've detected that you're a community contributor. @SarahFrench, a repository maintainer, has been assigned to assist you and help review your changes.

❓ First time contributing? Click here for more details

Your assigned reviewer will help review your code by:

  • Ensuring it's backwards compatible, covers common error cases, etc.
  • Summarizing the change into a user-facing changelog note.
  • Passes tests, either our "VCR" suite, a set of presubmit tests, or with manual test runs.

You can help make sure that review is quick by running local tests and ensuring they're passing in between each push you make to your PR's branch. Also, try to leave a comment with each push you make, as pushes generally don't generate emails.

If your reviewer doesn't get back to you within a week after your most recent change, please feel free to leave a comment on the issue asking them to take a look! In the absence of a dedicated review dashboard most maintainers manage their pending reviews through email, and those will sometimes get lost in their inbox.


@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 ( 5 files changed, 1130 insertions(+), 2 deletions(-))
Terraform Beta: Diff ( 5 files changed, 1130 insertions(+), 2 deletions(-))
TF Conversion: Diff ( 3 files changed, 160 insertions(+), 3 deletions(-))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2698
Passed tests 2401
Skipped tests: 279
Affected tests: 18

Action taken

Found 18 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
TestAccFirestoreField_firestoreFieldUpdateAddTTLExample|TestAccFirestoreField_firestoreFieldUpdateAddIndexExample|TestAccFirestoreField_firestoreFieldTimestampExample|TestAccFirestoreField_firestoreFieldBasicExample|TestAccFirestoreField_firestoreFieldMatchOverrideExample|TestAccCloudRunV2JobIamPolicyGenerated|TestAccCloudRunV2JobIamMemberGenerated|TestAccCloudRunV2JobIamBindingGenerated|TestAccDataSourceGoogleFirebaseAndroidAppConfig|TestAccCloudRunV2Job_cloudrunv2JobBasicExample|TestAccCloudRunV2Job_cloudrunv2JobFullUpdate|TestAccCloudRunV2Job_cloudrunv2JobVpcaccessExample|TestAccCloudRunV2Job_cloudrunv2JobSqlExample|TestAccAlloydbCluster_missingLocation|TestAccAlloydbBackup_missingLocation|TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample|TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example|TestAccDataSourceAlloydbLocations_basic

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

Tests passed during RECORDING mode:
TestAccFirestoreField_firestoreFieldUpdateAddTTLExample[Debug log]
TestAccFirestoreField_firestoreFieldUpdateAddIndexExample[Debug log]
TestAccFirestoreField_firestoreFieldTimestampExample[Debug log]
TestAccFirestoreField_firestoreFieldBasicExample[Debug log]
TestAccFirestoreField_firestoreFieldMatchOverrideExample[Debug log]
TestAccCloudRunV2JobIamPolicyGenerated[Debug log]
TestAccCloudRunV2JobIamMemberGenerated[Debug log]
TestAccCloudRunV2JobIamBindingGenerated[Debug log]
TestAccCloudRunV2Job_cloudrunv2JobBasicExample[Debug log]
TestAccCloudRunV2Job_cloudrunv2JobFullUpdate[Debug log]
TestAccCloudRunV2Job_cloudrunv2JobVpcaccessExample[Debug log]
TestAccCloudRunV2Job_cloudrunv2JobSqlExample[Debug log]
TestAccAlloydbCluster_missingLocation[Debug log]
TestAccAlloydbBackup_missingLocation[Debug log]
TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample[Debug log]
TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example[Debug log]
TestAccDataSourceAlloydbLocations_basic[Debug log]

Tests failed during RECORDING mode:
TestAccDataSourceGoogleFirebaseAndroidAppConfig[Error message] [Debug log]

Please fix these to complete your PR
View the build log or the debug log for each test

@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 ( 5 files changed, 1133 insertions(+), 2 deletions(-))
Terraform Beta: Diff ( 5 files changed, 1133 insertions(+), 2 deletions(-))
TF Conversion: Diff ( 3 files changed, 160 insertions(+), 3 deletions(-))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2711
Passed tests 2425
Skipped tests: 279
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
TestAccFirebaserulesRelease_BasicRelease|TestAccDataSourceGoogleFirebaseAndroidAppConfig|TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample|TestAccAlloydbCluster_missingLocation|TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example|TestAccAlloydbBackup_missingLocation|TestAccDataSourceAlloydbLocations_basic

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

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

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

@pcostell
Copy link
Contributor Author

pcostell commented May 2, 2023

@rwhogg or @clement would appreciate a Firestore-specific review as well.

Copy link
Contributor

@SarahFrench SarahFrench left a comment

Choose a reason for hiding this comment

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

This PR looks good to me in terms of how the downstream code generation works, how the tests are comprehensive, and that the tests pass.

I'm not super familiar with Firestore (I reviewed while referring to the docs) so I'm glad you've tagged others for a Firestore-specific review. Once you've responded to any feedback from them and are satisfied give me an @-mention and I can merge the PR :shipit:

properties:
- !ruby/object:Api::Type::String
name: 'database'
default_value: '(default)'
Copy link
Contributor

Choose a reason for hiding this comment

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

I was going to ask about this default value, and whether there should be an acceptance tests that sets database to another value, but then I saw this in the docs:

A Cloud Firestore Database. Currently only one database is allowed per cloud project; this database must have a databaseId of '(default)'.

Noting this on the PR partly for myself as I'm unfamiliar with Firestore, partly for the benefit of anyone looking at the PR in future!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 Once this restriction changes, I expect we should use generative ones for testing.

// Re-populate split fields from the name.
re := regexp.MustCompile("^projects/([^/]+)/databases/([^/]+)/collectionGroups/([^/]+)/fields/(.+)$")
match := re.FindStringSubmatch(d.Get("name").(string))
if len(match) > 0{
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: please add a space after the 0

collection = "chatrooms_%{random_suffix}"
field = "basic"

index_config {
Copy link
Contributor

Choose a reason for hiding this comment

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

👍🏻 on all of the examples included. If possible, could we also add one that explicitly shows how to create an SFI exclusion?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note these are all technically exclusions (they do not inherit from the ancestor configuration). The timestamp example covers the case where a user wants to completely disable their single field indexes. I added a comment there (and updated the description in the yaml) to make this more obvious.

Copy link
Contributor

@rwhogg rwhogg left a comment

Choose a reason for hiding this comment

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

Nice work!!! Left some largely-nitpicky comments.

@pcostell
Copy link
Contributor Author

pcostell commented May 3, 2023

Thank you both for the review! Comments should be addressed, PTAL

@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 ( 5 files changed, 1141 insertions(+), 2 deletions(-))
Terraform Beta: Diff ( 5 files changed, 1141 insertions(+), 2 deletions(-))
TF Conversion: Diff ( 3 files changed, 160 insertions(+), 3 deletions(-))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_firestore_field (3 total tests)
Untested fields: database

Please add acceptance tests which include these fields.

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2716
Passed tests 2429
Skipped tests: 279
Affected tests: 8

Action taken

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

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

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

Tests failed during RECORDING mode:
TestAccComputeFirewallPolicyRule_multipleRules[Error message] [Debug log]

Please fix these to complete your PR
View the build log or the debug log for each test

@pcostell
Copy link
Contributor Author

pcostell commented May 5, 2023

@SarahFrench I think this is ready for merge if you're happy with it.

pcostell added 3 commits May 5, 2023 12:10
Introduces a single resource for managing Firestore fields, matching the
REST API.

Introduces 2 primary divergences from the proto/REST API:

1) Firestore fields do not support deletion (this is because all fields
   implicitly can exist in a schemaless system). Deletion of a terraform
   resource will clear any "overrides" for this field (TTL or indexing).
2) Single field indexes in the proto API were overly nested to allow
   reusing the same resource for composite indexes. The terraform
   resource unnests the 1-length field in the indexes list.

fixes hashicorp/terraform-provider-google#12151
fixes hashicorp/terraform-provider-google#11419
@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 ( 5 files changed, 1144 insertions(+), 2 deletions(-))
Terraform Beta: Diff ( 5 files changed, 1144 insertions(+), 2 deletions(-))
TF Conversion: Diff ( 3 files changed, 160 insertions(+), 3 deletions(-))

Copy link
Contributor

@SarahFrench SarahFrench left a comment

Choose a reason for hiding this comment

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

LGTM - I'll let the tests run and will merge after assuming all is ok

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2716
Passed tests 2429
Skipped tests: 279
Affected tests: 8

Action taken

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

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

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

Tests failed during RECORDING mode:
TestAccComputeFirewallPolicyRule_multipleRules[Error message] [Debug log]

Please fix these to complete your PR
View the build log or the debug log for each test

@SarahFrench
Copy link
Contributor

Failed test is unrelated, merging

@SarahFrench SarahFrench merged commit a9c721c into GoogleCloudPlatform:main May 5, 2023
ericayyliu pushed a commit to ericayyliu/magic-modules that referenced this pull request Jul 26, 2023
* Introduce google_firestore_field resource.

Introduces a single resource for managing Firestore fields, matching the
REST API.

Introduces 2 primary divergences from the proto/REST API:

1) Firestore fields do not support deletion (this is because all fields
   implicitly can exist in a schemaless system). Deletion of a terraform
   resource will clear any "overrides" for this field (TTL or indexing).
2) Single field indexes in the proto API were overly nested to allow
   reusing the same resource for composite indexes. The terraform
   resource unnests the 1-length field in the indexes list.

fixes hashicorp/terraform-provider-google#12151
fixes hashicorp/terraform-provider-google#11419

* Address feedback in review (mostly minor cleanups).

* Fix whitespace and add database to basic example.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants