-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Virtual field for google_cloud_run_service
revision names
#3306
Virtual field for google_cloud_run_service
revision names
#3306
Conversation
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 pretty sure this allows for both manual revision management and auto and it works pretty well from my local testing, thanks! Can you add autogenerate_revision_name = true
to one of the examples?
products/cloudrun/terraform.yaml
Outdated
description: | | ||
If set to `true`, the revision name (template.metadata.name) will be omitted and | ||
autogenerated by Cloud Run. This cannot be set to `true` while `template.metadata.name` | ||
is also set. |
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.
It might be good to clarify somewhere that if name
isn't in the config and this is false it will still be managed server side for legacy support.
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 3 files changed, 37 insertions(+), 2 deletions(-)) |
…oudPlatform#3306) * Add `autogenerate_revision_name` virtual field to `google_cloud_run_service` * Add field to examples
Fixes hashicorp/terraform-provider-google#5898
Release Note Template for Downstream PRs (will be copied)