bbe0f31080
There are some API resources, like e.g. flavors or service_profiles which don't require tenant_id/project_id attribute. But such attributes were always added to every resource in every POST request. That forced to add tenant_id attribute to the definition of every resource otherwise validation of the attributes during POST call was failing. Now, tenant_id/project_id are added to the resource's dict only in case when resource definiton really defines that resource requires it. This patch removes tenant_id from the definiton of the resources which don't really require it so it won't be added to it's dict during POST request anymore. Depends-On: https://review.opendev.org/c/openstack/neutron/+/922716 Depends-On: https://review.opendev.org/c/openstack/neutron/+/921647 Depends-On: https://review.opendev.org/c/openstack/neutron/+/922790 Closes-Bug: #2022043 Change-Id: Iad1e335a1e232b308017a2886916fa9ec0d068c4
9 lines
370 B
YAML
9 lines
370 B
YAML
---
|
|
other:
|
|
- |
|
|
API resources which do not really have ``project_id`` associated with them,
|
|
because either it belongs to the project to which their parent belongs (``QoS
|
|
rules``) or does not belong to any project (``flavor`` and ``service
|
|
profile``), do not accept ``project_id`` nor ``tenant_id`` to be sent in the
|
|
body of the POST or PUT request.
|