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 validation on Cloud Functions available_memory_mb #4702

Merged
merged 2 commits into from
Apr 19, 2021

Conversation

rileykarson
Copy link
Member

I saw a question about whether we support 8GB (8192) of memory or not because it was introduced in the API, and we don't- these values have changed out of band a few times, and I don't feel that this validation is helpful enough to be worth keeping up with value churn. Also note that our docs never reflected supporting 4GB- I figure it's clear enough what the pattern for 2048/4096/8192 will be, so I just changed values past 1024 to "etc".

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)

cloudfunctions: removed bounds on the supported memory range in `google_cloudfunctions_function.available_memory_mb`

@google-cla google-cla bot added the cla: yes label Apr 15, 2021
@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 ( 2 files changed, 2 insertions(+), 20 deletions(-))
Terraform Beta: Diff ( 3 files changed, 3 insertions(+), 22 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=182530"

@rileykarson
Copy link
Member Author

/gcbrun

@rileykarson rileykarson requested review from a team and melinath and removed request for a team April 15, 2021 19:06
@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 ( 2 files changed, 2 insertions(+), 20 deletions(-))
Terraform Beta: Diff ( 3 files changed, 3 insertions(+), 21 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=182546"

Copy link
Member

@melinath melinath left a comment

Choose a reason for hiding this comment

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

LGTM

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.

3 participants