Check for existing issues
The Feature
In terraform/litellm/gcp, support organizations that enforce Domain Restricted Sharing (DRS), where allUsers IAM bindings are rejected.
Today the module creates roles/run.invoker IAM members with member = "allUsers" for each Cloud Run service. In DRS-constrained orgs this fails policy checks and blocks deployment.
Requested change:
- Set
invoker_iam_disabled = true on each google_cloud_run_v2_service resource in this module (gateway, backend, ui)
- Stop relying on
allUsers run.invoker bindings for these services in DRS environments
- Document this behavior in module docs and any migration notes
User Flow
Before this feature (today): deployment fails in DRS-enforced orgs because the module applies allUsers invoker grants
- Operator runs
terraform apply for terraform/litellm/gcp
- Cloud Run services are created
- Module attempts to apply
google_cloud_run_v2_service_iam_member resources with member = "allUsers"
- Organization policy rejects the binding and apply fails
After this feature (ideal user flow): the same deployment succeeds without requiring allUsers invoker bindings
- Operator runs
terraform apply for terraform/litellm/gcp
- Cloud Run services are created with
invoker_iam_disabled = true
- Module does not require
allUsers run.invoker IAM members for service reachability
- Apply succeeds in DRS-constrained orgs
How far you got
Config / setup the proxy ran with:
- Module path:
terraform/litellm/gcp
- Cloud Run services in module:
gateway, backend, ui
Version or commit:
- Current repository state at time of issue filing
Commands and their full output, up to the step that dead-ends:
# terraform apply in terraform/litellm/gcp (or example root)
# apply reaches Cloud Run IAM member creation for allUsers
# org policy rejects allUsers member in DRS-constrained orgs
│ Error: Error applying IAM policy for cloudrunv2 service "projects/<project>/locations/us-east5/services/litellm-prod-gateway": Error setting IAM policy for cloudrunv2 service "projects/<project>/locations/us-east5/services/litellm-prod-gateway": googleapi: Error 400: One or more users named in the policy do not belong to a permitted customer, perhaps due to an organization policy.
│
│ with module.litellm.google_cloud_run_v2_service_iam_member.gateway_allusers,
│ on cloudrun.tf line 493, in resource "google_cloud_run_v2_service_iam_member" "gateway_allusers":
│ 493: resource "google_cloud_run_v2_service_iam_member" "gateway_allusers" {
│
What stopped me there:
- DomainRestrictedSharing policy rejects
allUsers IAM member bindings, causing module apply failure.
What part of LiteLLM is this about?
Proxy
LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?
No
Twitter / LinkedIn details
N/A
Check for existing issues
The Feature
In
terraform/litellm/gcp, support organizations that enforce Domain Restricted Sharing (DRS), whereallUsersIAM bindings are rejected.Today the module creates
roles/run.invokerIAM members withmember = "allUsers"for each Cloud Run service. In DRS-constrained orgs this fails policy checks and blocks deployment.Requested change:
invoker_iam_disabled = trueon eachgoogle_cloud_run_v2_serviceresource in this module (gateway,backend,ui)allUsersrun.invokerbindings for these services in DRS environmentsUser Flow
Before this feature (today): deployment fails in DRS-enforced orgs because the module applies
allUsersinvoker grantsterraform applyforterraform/litellm/gcpgoogle_cloud_run_v2_service_iam_memberresources withmember = "allUsers"After this feature (ideal user flow): the same deployment succeeds without requiring
allUsersinvoker bindingsterraform applyforterraform/litellm/gcpinvoker_iam_disabled = trueallUsersrun.invokerIAM members for service reachabilityHow far you got
Config / setup the proxy ran with:
terraform/litellm/gcpgateway,backend,uiVersion or commit:
Commands and their full output, up to the step that dead-ends:
What stopped me there:
allUsersIAM member bindings, causing module apply failure.What part of LiteLLM is this about?
Proxy
LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?
No
Twitter / LinkedIn details
N/A