You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/07/02 22:44:09 UTC
[GitHub] rawlinp opened a new issue #2496: TO Go PUT ASNs, regions,
and tenants endpoints now require "id" field in request (possibly breaking
clients)
rawlinp opened a new issue #2496: TO Go PUT ASNs, regions, and tenants endpoints now require "id" field in request (possibly breaking clients)
URL: https://github.com/apache/trafficcontrol/issues/2496
The following TO Go PUT endpoints now appear to require `"id": <id>` in the request body even though the Perl API did not require this (`id` is already a required path parameter):
PUT /asns/{id} ("id" key/value omitted from request body):
```
{
"alerts": [
{
"level": "error",
"text": "unable to parse required keys from request body"
}
]
}
```
PUT /regions/{id} ("id" key/value omitted from request body):
```
{
"alerts": [
{
"level": "error",
"text": "key in body does not match key in params"
}
]
}
```
PUT /tenants/{id} ("id" key/value omitted from request body):
```
{
"alerts": [
{
"level": "error",
"text": "key in body does not match key in params"
}
]
}
```
Since `"id"` is now erroneously a required field, some clients might be broken; however, Traffic Portal is unaffected because it appears to always send the `"id"` field in PUT requests.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services