Remove API description where Tacker doesn't have endpoints from API-DQ
Bug #1913665 reported by
Hiroo Kitamura
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
Fix Released
|
Wishlist
|
Hiroo Kitamura | ||
Bug Description
In the following VNF LCM API document, there is a `Notification` API where Tacker doesn't have an endpoint.
https:/
As an API specification, I think that only APIs where Tacker has an endpoint as a Server should be described.
Therefore, it is necessary to modify the following files and delete the Notification definition.
https:/
* api-ref/
* api-ref/
* api-ref/
| Changed in tacker: | |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Hiroo Kitamura (h-kitamura) |
Revision history for this message
| Hiroo Kitamura (h-kitamura) wrote | #1 |
| Changed in tacker: | |
| status: | New → In Progress |
| Changed in tacker: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tacker 5.0.0.0rc1 | #2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/