-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Add temp_bucket parameter for resource google_dataproc_cluster (#7927) #4375
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=165840" |
I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccInstanceTemplateDatasource_name|TestAccInstanceTemplateDatasource_filter|TestAccInstanceTemplateDatasource_filter_mostRecent|TestAccDataSourceGoogleSubnetwork|TestAccDataSourceStorageBucketObjectContent_Basic|TestAccActiveDirectoryDomainTrust_activeDirectoryDomainTrustBasicExample|TestAccContainerCluster_withConfidentialNodes|TestAccContainerCluster_withPrivateClusterConfigMissingCidrBlock|TestAccDataprocAutoscalingPolicy_dataprocAutoscalingPolicyExample|TestAccDataprocClusterIamBinding|TestAccDataprocCluster_withTempBucket|TestAccDataprocClusterIamPolicy|TestAccDataprocClusterIamMember|TestAccDataprocCluster_withMetadataAndTags|TestAccDataprocCluster_withAccelerators|TestAccDataprocCluster_withInternalIpOnlyTrue|TestAccDataprocCluster_singleNodeCluster|TestAccDataprocCluster_updatable|TestAccDataprocCluster_withStagingBucket|TestAccDataprocCluster_withInitAction|TestAccDataprocCluster_withImageVersion|TestAccDataprocCluster_withConfigOverrides|TestAccDataprocCluster_withOptionalComponents|TestAccDataprocCluster_withLifecycleConfigIdleDeleteTtl|TestAccDataprocCluster_withEndpointConfig|TestAccDataprocCluster_withAutoscalingPolicy|TestAccDataprocCluster_withKerberos|TestAccDataprocJobIamBinding|TestAccDataprocJob_Spark|TestAccDataprocCluster_withServiceAcc|TestAccDataprocJob_updatable|TestAccDataprocJobIamPolicy|TestAccDataprocJob_PySpark|TestAccDataprocJobIamMember|TestAccDataprocJob_Hadoop|TestAccDataprocJob_Hive|TestAccDataprocCluster_KMS|TestAccDataprocJob_Pig|TestAccDataprocJob_SparkSql You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=165854" |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=166040" |
I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccInstanceTemplateDatasource_filter|TestAccInstanceTemplateDatasource_filter_mostRecent|TestAccDataSourceGoogleSubnetwork|TestAccDataSourceGoogleServiceAccountIdToken_impersonation|TestAccDataSourceStorageBucketObjectContent_Basic|TestAccActiveDirectoryDomainTrust_activeDirectoryDomainTrustBasicExample|TestAccContainerCluster_withConfidentialNodes|TestAccContainerCluster_withPrivateClusterConfigMissingCidrBlock|TestAccDataprocJob_Spark You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=166056" |
dataproc tests failing on this branch are also failing on master; I believe they are unrelated to these changes. |
you should link the issue like closes 7927 since the issue exists on a separate repo you can't do the hash. Use a quantified link so it will auto close on completion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know much about ... so adding @slevenick for a second pass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will need the field to be added to the docs so that it will show up on the website
{ | ||
// Simulate destroy of cluster by removing it from definition, | ||
// but leaving the temp bucket (should not be auto deleted) | ||
Config: testAccDataprocCluster_withTempBucketOnly(bucketName), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really sure why this step is here. It seems to be testing that deleting the cluster does not delete the storage bucket, but I'm not sure why we would be concerned about that. Declaring the storage bucket in a TF config and ensuring that it exists should be covered by storage bucket tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@slevenick I believe the contributor copy-pasted this from the storage bucket tests directly above. My assumption was that there was a concern that GCP might auto-delete the related storage (or temp) bucket resource without terraform being able to control it.
If you think this is unnecessary, I can definitely ask them to remove it & open a ticket to update the storage_bucket tests as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
talked with Sam - it's okay to leave this in place since it is the same as the other test.
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=168384" |
@slevenick documentation added! |
Upstreamed from hashicorp/terraform-provider-google#8131. According to the docs the missing CLA is not an issue since this only changes third_party?
Allow using
temp_bucket
when creating a Dataproc cluster as addressed in hashicorp/terraform-provider-google#7927.Closes hashicorp/terraform-provider-google#7927.
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)