This extension indicates if Neutron supports checking the resource
usage before applying a new quota limit.
Change-Id: I94baf069624da4e4009eb8c0820f91b4d9e6738f
Related-Bug: #1936408
The tags for neutron-in-tree-api-ref remain there.
This patch makes quotas api-ref cler more and then removes the tags.
Change-Id: If43a8a5c82f08925703cbd4500abbea2c043fe25
For consistency.
Also,
- Sort codes in "Error responce codes"
- Remove 5xx from "Error response codes"
- Move 2xx to "Normal response codes"
This is mechanically done by applying the following on each *.inc:
gawk -F": " 'function p(h,a){r=s="";asort(a);
for(i in a){r=r s a[i];s=", "};print h ": " r}
/^Error response codes:/{split($2,a,/[, ]*/);
delete n;ni=1;delete e;ei=1;
for(i in a){x=a[i];v=x-x%100;if(v==200)n[ni++]=x;
else if(v!=500)e[ei++]=x};
if(ni>1){p("Normal response codes",n);
print ""};p($1,e);next}//{print}'
Change-Id: I5447e660117e56b057d2b2cf509666a1d56e63bf
project_id and tenant_id field in request/response body are
marked as "path" now. It should be "body".
- "project_id-path" already exists and it can be used
for "project_id" in URL path.
- "project_id" is now used for body.
- "project_id-body" is now duplicated, so it was removed.
fwaas.inc is the only user of project_id-body and
it is updated accordingly.
- quotas.inc is updated to use 'project_id-path'.
Also project_id and tenant_id in response body of a quotas operation
have been dropped as they do not exist.
Note that project_id/tenant_id in request body should be marked
as "optional" in most resources but this patch does not touch them
to avoid unnecessary merge conflicts.
They will be fixed in separate patches.
Change-Id: Ic5a4f55b837ee0a51b7186c3342a94c8c00f6c97
Closes-Bug: #1650174
Use 'project' instead of 'tenant' in descriptions.
Accept either 'tenant_id' or 'project_id' in requests.
Return both 'tenant_id' or 'project_id' in responses.
Related Blueprint: keystone-v3
Change-Id: I606f7399dfb824ba08922470f6e46b0a150af33b
Previously sample JSON files are placed in the top directory
of api-ref, but they belong to v2 API, so it sounds reasonable
to place them in v2 directory.
Preparation of API-ref cleanup.
Part of blueprint neutron-in-tree-api-ref
Change-Id: I7c63f570507c51526957988f9b21a4244bd6e58a