-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Cannot create an App Engine NEG with default routing #15593
Cannot create an App Engine NEG with default routing #15593
Comments
Also encountered this limitation. The workaround seems to be to create separate NEG and Backend Services per App Engine service and move the routing to the load balancer. Frustrating given how simple it is to use the default routing via the Google Console. |
If the issue is that Possibly relevant context: |
Double-checked and it's already set up that way, except that it's missing I can reproduce this with the following config:
|
Fix is waiting in GoogleCloudPlatform/magic-modules#9980 |
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. |
Community Note
Terraform Version
Terraform v1.5.5
on darwin_arm64
+ provider registry.terraform.io/hashicorp/google-beta v4.79.0
Description
When creating a serverless NEG pointing to App Engine, there's an option called "Default routing", which targets the App Engine application in general, not any specific service or version. This is useful for defining internal routing rules in the application, using the
dispatch.yaml
configuration file.Creating the NEG on the GCP console looks like this:
However, it doesn't seem that current Terraform code supports that feature. The resource required to create a NEG is compute_region_network_endpoint_group. The
app_engine
block inside that resource defines 3 optional arguments:service
,version
andurl_mask
. Specifying only one of those voids the intent of default routing, and leaving the block empty is not valid as it generates an API error when trying to create the resource:The above error can be reproduced with the following resource definition:
New or Affected Resource(s)
Potential Terraform Configuration
One option to solve this could be to add a new flag inside the
app_engine
block named "default_routing" or similar, to be explicit about creating an App Engine NEG:References
b/312433182
The text was updated successfully, but these errors were encountered: