dd5976b7ab
Update the API to accept project_id in requests and return project_id in responses. For now, the API treats tenant_id and project_id equivalently. It accepts either or both in requests. It returns both in responses, depending on filters. We include an extension to indicate that support for project_id is enabled in the API. Completes: blueprint keystone-v3 APIImpact: Describe how the Networking API supports Keystone V3. Co-Authored-By: Henry Gessau <HenryG@gessau.net> Co-Authored-By: Akihiro Motoki <amotoki@gmail.com> Change-Id: I8775aa8a477191ef21e7c3c6da31d098befefc3c
8 lines
390 B
YAML
8 lines
390 B
YAML
---
|
|
features:
|
|
- The Networking API now supports the 'project_id' field in requests and
|
|
responses, for compatibility with the Identity (Keystone) API V3. A new
|
|
API extension, 'project-id', has been added to allow API users to detect
|
|
if the 'project_id' field is supported. Note that the 'tenant_id' field
|
|
is still supported, and the two fields are functionally equivalent.
|