`services create --from` fails for non-Enterprise users due to IP allow list

[Andrej730]

Description

Running render services create --from <id> fails with:

Error: received response code 400: IP allow list is only available for Enterprise workspaces

Render automatically sets an IP allow list (0.0.0.0/0, everywhere) on every new service. When --from clones the source service, it includes this IP allow list in the create request, which the API rejects for non-Enterprise workspaces.

This makes --from effectively unusable for non-Enterprise users. While the IP allow list is visible in Dashboard Settings, it cannot be removed on non-Enterprise plans.

Steps to reproduce

Every new service automatically gets an IP allow list set, visible via:

$ render services --output json | python -m json.tool | grep -A4 "ipAllowList"
        "ipAllowList": [
            {
                "cidrBlock": "0.0.0.0/0",
                "description": "everywhere"
            }

Running render services create --from <id> then fails:

$ render services create --from srv-xxx --name my-service --region ohio --output json
Error: received response code 400: IP allow list is only available for Enterprise workspaces

Expected behavior

One of:

1. New services should not have an IP allow list set internally by default
2. --from should skip copying the IP allow list for this case with non-Enterprise users
3. Add a --no-ip-allow-list flag to suppress it when cloning

Workaround

Use render services create and pass all parameters manually instead of using --from.