-
Notifications
You must be signed in to change notification settings - Fork 90
Closed
Milestone
Description
Background
According to the CF API, user can specify a port number when creating routes. That port only makes sense for TCP routes.
Korifi does not support TCP routes, however the API invocation should not fail if port is specified
Acceptance
WHEN I create a route via
curl "https://api.example.org/v3/routes" \
-X POST \
-H "Authorization: bearer [token]" \
-H "Content-type: application/json" \
-d '{
"host": "a-hostname",
"path": "/some_path",
"port": 6666,
"relationships": {
...
},
}'
THEN I get a HTTP 201 created response
Dev notes:
- Spike commit: ae21407
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
✅ Done