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

Assume scratch disk size when not returned by the API #4014

Merged

Conversation

c2thorn
Copy link
Member

@c2thorn c2thorn commented Sep 24, 2020

Fixes hashicorp/terraform-provider-google#7341

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).
  • Generated Terraform, and ran make test and make lint to ensure it passes unit and linter tests.
  • 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).
  • Ran relevant acceptance tests (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)

compute: fixed an issue where `google_compute_instance_template` would throw an error for unspecified `disk_size_gb` values while upgrading the provider.

@google-cla google-cla bot added the cla: yes label Sep 24, 2020
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 1 file changed, 12 insertions(+), 3 deletions(-))
Terraform Beta: Diff ( 1 file changed, 12 insertions(+), 3 deletions(-))

@modular-magician
Copy link
Collaborator

I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=148442"

@c2thorn
Copy link
Member Author

c2thorn commented Sep 24, 2020

Ran all the instance template tests in the TPGB MM upstream build, all passing.

@c2thorn c2thorn requested a review from slevenick September 24, 2020 22:21
@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccDataSourceDnsManagedZone_basic|TestAccProviderMeta_setModuleName|TestAccBigQueryJob_bigqueryJobCopyTableReferenceExample|TestAccComputeDisk_deleteDetach|TestAccComputeInstanceTemplate_withScratchDisk|TestAccComputeInstance_diskEncryption|TestAccComputeInstance_kmsDiskEncryption|TestAccComputeInstance_bootDisk_source|TestAccComputeInstance_bootDisk_sourceUrl|TestAccComputePerInstanceConfig_update|TestAccComputeRegionDisk_deleteDetach|TestAccComputeRegionPerInstanceConfig_update|TestAccComputeSnapshot_encryptionCMEK You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=148447"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

provider 2.20.0 -> 3.40.0 google_compute_instance_template scratch disk validation anomalies
3 participants