Closed SeanKilleen closed 11 months ago
Just as a follow up to this -- after some deeper reading on the syntax and based on the V3 API docs, I see that I might need to not specify a router group when attempting to create a shared internal TCP domain.
Once I understood the V3 API syntax enough to call it directly via cf curl
, I realized that the request requires full admin permissions, so I'll need to obtain those or have someone else execute. Once I attempt that, I'll add more notes here on whether my permissions issue affected the output here.
My guess is that the CLI v8 is still hitting an old endpoint since it looks like it's looking for a /v1
URL rather than a /v3
. But I'm also very new and so am more inclined to believe it's my fault first. 😄
I finally found some documentation on the SAP side that shows it wasn't a CF issue at all.
https://help.sap.com/docs/btp/sap-business-technology-platform/cloud-foundry-environment
TCP based networking and internal routes are supported in CloudFoundry but not SAP BTP.
That's a bummer for me personally, but it's not CF's fault 😆 I wanted to follow up on this and close it before anyone spent too much time on it.
Please fill out the issue checklist below and provide ALL the requested information.
CF_TRACE=1
to help debug the issue.Describe the bug and the command you saw an issue with
Goal: I am in the context of an SAP BTP environment CloudFoundry environment, which uses standard CF CLI tooilng. I am attempting to create a new internal TCP route for a clustering scenario. My understanding is that upon creating this shared internal TCP route and mentioning it in my manifest, the cf push command will apply index-based routing.
I am logged in to the CF cli via
cf login
and can execute other commands successfully.However, whenever I run
cf router-groups
orcf create-shared-domain tcp.apps.internal --router-group default-tcp --internal
I see output similar to the following (with CF_TRACE=1):
For getting the routes:
This also hinders my ability to create a domain via the CloudFoundry Terraform provider (I see similar errors when it attempts to run
terraform plan
and calls the CLI.)Expected behavior
I can list the router-groups and create a TCP-based internal route.
Exact Steps To Reproduce Steps to reproduce the behavior; include the exact CLI commands and verbose output:
cf router-groups
to attempt to see (presumably) thedefault-tcp
router.Provide more context
cf curl /v2/info
:Notes regarding V6 and V7 CLI support: