4e6eec5c9beb0086ab370f5506ab73efe1705631
11 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
ghanshyam
|
f44d1aff9d |
Enable all extension for all remaining sample tests
As extensions options has been deprecated, API sample tests should run against all extension enable. This commit enables all extensions for all the remaining sample tests and remove extensions specific tests and sample files. Also remove extension setting specific logic from base test class along with TODOs. Partially implements blueprint api-sample-tests-with-all-extensions Change-Id: I66b593760789e5b3b92137a672246f8d91e44cba |
||
|
Sean Dague
|
c9f5ad3bcf |
remove /v2.1/{tenant_id} from all urls
As discussed at summit, the version part of the URL is not really relevant, or a thing a user should be filling out themselves, this should instead be set by the service catalog and extracted from the token. This removes it's reference in all documented REST urls, and adds a new section describing how one gets the base URL for all calls. Change-Id: I4306b8c3de0225e54f3909dd8a1fb293c4e5944c |
||
|
Sean Dague
|
04f8612aa9 |
api-ref: complete verification for extensions resource
This completes all 4 phases of the extensions resource. * List method was added * Error codes updated as exist in code * Updates parameters.yaml to match actual descriptions for parameters * Update body to be a lot stronger about what our deprecation means and why. Part of bp:api-ref-in-rst Change-Id: I003fc1cc84cd429fbdc0c4f0847be81d920d3561 |
||
|
sharat.sharma
|
75280e582e |
Deprecated the concept of extensions in v2.1.
The extensions in api-ref-compute-v2.1 is deprecated. This patch depricates the extension infrastructure in v2.1. Change-Id: Ie7731c25ee7c5c662c22835add3314ffa51f37bc Closes-Bug: #1490531 |
||
|
Sean Dague
|
d929b9fc76 |
add tags to files for the content verification phase
This adds a set of tags in comments to the beginning of files so that we can process them according to the documentation here: https://wiki.openstack.org/wiki/NovaAPIRef Part of bp:api-ref-in-rst Change-Id: I17cf584dafb5bd969c12f51b7e7185d92365bf93 |
||
|
Sean Dague
|
f208917c52 |
Fix remaining json reference warnings
This fixes the last json reference warning which exist. It also trims out the baremetal API calls that we don't support any more (we only have the readonly proxy). That was erroneously added to the compute API docs in refactors of api-site last cycle. Change-Id: I08be639b610304049b0959902ed8876559111274 |
||
|
Jenkins
|
c787a8361f | Merge "Fix diagnostics, extensions api ref" | ||
|
ghanshyam
|
6f8cda2f39 |
Fix json response example heading in api ref
Heading for json response example is wrong, it is json request instead of json response. Part of bp:api-ref-in-rst Change-Id: I709b2bf19520eb76e0264c358a2146bb0dbcee2b |
||
|
jichenjc
|
17c09561f4 |
Fix diagnostics, extensions api ref
update those files api-ref Part of bp:api-ref-in-rst Change-Id: Id68dbc77011a7414edda5a4855ccbddb204031ac |
||
|
Sean Dague
|
9526462326 |
move sphinx h3 to '-' instead of '^'
In the sphinx document h3 is supposed to be '-' not '^': =, for sections -, for subsections ^, for subsubsections We have to enforce consistency here because we're processing included files which all have to agree, otherwise it's a sphinx error. Part of bp:api-ref-in-rst Change-Id: Ic6eef5cacb07870f161b04b031e332f2b87aeedc |
||
|
Sean Dague
|
d4e2771440 |
Import RST files for documentation
This is the results of the RST conversion from WADL. It creates a single index plus a bunch of included files which represent sections of the API document. This is the starting point for fixing the documentation. Change-Id: I7d561c2ecdcd864172dedb54a551f17ad3bdfe26 |