-
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
Allow specifying 'container_port' and 'request_timeout' for google_cloud_run_service #5539
Allow specifying 'container_port' and 'request_timeout' for google_cloud_run_service #5539
Comments
I just stumbled on this issue as well. To provide more context to the issue:
In Cloud Run container instances, the The current way to deploy Cloud Run with Terraform makes us hardcode this and is currently not the best practice. You can add the env option:
This will come up as:
I checked the GCP Logging and it states:
Terraform will give: I tried with a fresh project and now get the following: Terraform Debug
Looks like Env option is broken as well. When I comment the |
I would like to have this feature too, this change was made in the January 7 release together with the option to deploy from a knative yaml file |
@remorses Do you know how to customise the container port? The release notes say it is now possible, but not how. Any idea where I can find the docs for this? Thanks. |
Someone should update the terraform provider to do so, unfortunately the provider is not updated by the google devs themselves so you just need to wait |
This change was made to enable cloud functions to be setup using terraform. See issue here: hashicorp/terraform-provider-google#5539
This change was made to enable cloud functions to be setup using terraform. See issue here: hashicorp/terraform-provider-google#5539
Is there any update on this issue? |
Waiting on this |
any updates? |
Has there been any updates on this issue, its breaking pretty much all of our deployments on the first run or we have to accomodate to the default port 8080! |
Isn't |
Also reproduced the fact that adding a PORT env results in:
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
Description
When deploying a Managed Cloud Run service in the GCP Web UI, the 'Container Port' and 'Request Timeout' options can be changed.
When deploying a Managed Cloud Run service with Terraform, there is no configuration available to change the 'Container Port' and 'Request Timeout' options away from default values.
I would like to be able to set these options when deploying Managed Cloud Run services with Terraform, instead of using the default values.
New or Affected Resource(s)
google_cloud_run_service
Potential Terraform Configuration
References
https://www.terraform.io/docs/providers/google/r/cloud_run_service.html
https://console.cloud.google.com/run
The text was updated successfully, but these errors were encountered: