nfv/nfv/nfv-vim/nfv_vim/api
Al Bailey 7ca02243d1 Adding details to VIM API Conflict responses
When the VIM Stragegy API returns a 409 Conflict for a create,
it is much more useful to know details about the conflict.
ie:  what type of strategy already exists.

This fix required:
 - the strategy creation rpc message adds an error string
 - pecan.abort 'conflict' must include the error string
 - the nfv_client code must extract the error string
 - the strategy types must return knowledge of an existing
strategy type
 - the director class must include details of the existing
strategy type in its failure messages.

Test Plan:
  PASS: Create two patch strategies and view the error.
  PASS: Create two different strategies and view the error.
  PASS: View errors when creating multiple strategies
       from horizon.

Closes-Bug: #1989485
Signed-off-by: Al Bailey <al.bailey@windriver.com>
Change-Id: Ic79eab03b70b8bc7fbe2876f95eea3f2f34ab791
2022-09-14 00:21:46 +00:00
..
acl Support Reader Role for sw-manager 2022-08-26 09:42:47 -04:00
controllers Adding details to VIM API Conflict responses 2022-09-14 00:21:46 +00:00
openstack Support Reader Role for patch-strategy 2022-08-24 19:53:27 +00:00
__init__.py Clean up imports based on flake8 2018-09-20 16:43:28 -05:00
_application.py Support Reader Role for patch-strategy 2022-08-24 19:53:27 +00:00
_config.py StarlingX open source release updates 2018-05-31 07:36:51 -07:00
_hooks.py Support Reader Role for patch-strategy 2022-08-24 19:53:27 +00:00
_link.py StarlingX open source release updates 2018-05-31 07:36:51 -07:00