The following proposed API guidelines are available for broader
review by interested parties.
* https://review.openstack.org/#/c/281511/
Delete multiple metadata items with a single request
* https://review.openstack.org/#/c/260292/
Add unexpected attribute guideline
*
Hi All,
The following API guideline is ready for final review. It will be merged on
March 18, if there's no further feedback.
1. Header non-proliferation guideline
https://review.openstack.org/#/c/280381/
Cheers,
Everett
There are a couple of API-WG proposed guidelines ready for review by
interested parties:
Header non proliferation:
https://review.openstack.org/#/c/280381/
Client interaction guideline for microversions:
https://review.openstack.org/#/c/243414/
Please have a look at leave your
hi all,
The following API guideline is ready for cross project review. It will
be merged on Feb. 9 if there is no further feedback.
1. Must not return server-side tracebacks
https://review.openstack.org/#/c/183599
regards,
mike
hi all,
The following API guideline is ready for cross project review. It will
be merged on Jan. 21 if there is no further feedback.
1. Add description of pagination parameters
https://review.openstack.org/#/c/190743
regards,
mike
Everett Toews wrote:
> The following API guidelines are ready for cross project review. They will be
> merged on Nov. 20 if there's no further feedback.
> [...]
I see you added this topic for the next cross-project meeting. Would you
mind chairing that meeting ? I'm traveling with limited
Hi All,
The following API guidelines are ready for cross project review. They will be
merged on Nov. 20 if there's no further feedback.
1. Add introduction for API micro version guideline
https://review.openstack.org/#/c/187112/
2. Add description of pagination parameters
On Nov 13, 2015, at 12:55 PM, Everett Toews wrote:
>> Specifically this patch, or the ones dependent on it? Because this specific
>> patch doesn't actually say anything.
>
> Specifically this patch. Just looking to initially move forward in some small
> way on
> On Nov 13, 2015, at 12:01 PM, John Dickinson wrote:
>
>
>
> On 13 Nov 2015, at 9:42, Everett Toews wrote:
>
>> Hi All,
>>
>> The following API guidelines are ready for cross project review. They will
>> be merged on Nov. 20 if there's no further feedback.
>>
>> 1. Add
On 13 Nov 2015, at 9:42, Everett Toews wrote:
> Hi All,
>
> The following API guidelines are ready for cross project review. They will be
> merged on Nov. 20 if there's no further feedback.
>
> 1. Add introduction for API micro version guideline
> https://review.openstack.org/#/c/187112/
Hi All,
The following API guidelines are ready for cross project review. They will be
merged on Oct. 16 if there's no further feedback.
1. Adds an API documentation guideline document
https://review.openstack.org/#/c/214817/
2. Add http400 for nonexistent resource
On Aug 27, 2015, at 10:48 AM, Everett Toews wrote:
> Hi All,
>
> The following API guidelines are ready for cross project review. They will be
> merged on Sept. 4 if there's no further feedback.
>
> 1. Add description of pagination parameters
>
Hi All,
The following API guidelines are ready for cross project review. They will be
merged on Sept. 4 if there's no further feedback.
1. Add description of pagination parameters
https://review.openstack.org/#/c/190743/
2. Require OpenStack- in headers
https://review.openstack.org/#/c/215683/
Everett Toews wrote:
The following API guidelines are ready for cross project review. They will be
merged on Sept. 4 if there's no further feedback.
1. Add description of pagination parameters
https://review.openstack.org/#/c/190743/
2. Require OpenStack- in headers
On 08/11/2015 10:28 AM, michael mccune wrote:
1. Add new guideline for HTTP Headers
https://review.openstack.org/#/c/186526/
2. Add advice on when to use POST or PUT in create
https://review.openstack.org/#/c/181912/
3. Clarify the return code when server have hard-code length limit
On 08/11/2015 10:28 AM, michael mccune wrote:
1. Add new guideline for HTTP Headers
https://review.openstack.org/#/c/186526/
2. Add advice on when to use POST or PUT in create
https://review.openstack.org/#/c/181912/
3. Clarify the return code when server have hard-code length limit
hi all,
we have 3 API Guidelines that are ready for final review.
1. Add new guideline for HTTP Headers
https://review.openstack.org/#/c/186526/
2. Add advice on when to use POST or PUT in create
https://review.openstack.org/#/c/181912/
3. Clarify the return code when server have hard-code
Hi All,
We have 7 API Guidelines that are ready for a final review.
1. Add section clarifying PUT vs PATCH semantics
https://review.openstack.org/#/c/183945/
2. Adding 5xx guidance
https://review.openstack.org/#/c/183698/
3. Adds a small update to tagging guidance
hi all,
we have 1 API guideline that is ready for final review
1. Adds clarifications on state-conflicting requests
https://review.openstack.org/#/c/180094
if the API working group hasn't received any further feedback, we'll
merge this on July 3.
regards,
mike
Hi All,
We have 3 API Guidelines that are ready for a final review.
1. Add section on filtering
https://review.openstack.org/#/c/177468/
2. http guideline expansion: background
https://review.openstack.org/#/c/181931/
3. Should not return server-side tracebacks
20 matches
Mail list logo