Zane Bitter 714d9eea4c Handle resource plugins without default_client_name ... We want to be able to call is_not_found() or is_conflict() from the client plugin from the Resource class, regardless of what resource plugin is implementing the resource type. This is only possible when the default_client_name is set, which is optional for plugins to do. As a result, when handling an exception we need to check explicitly that there is a default_client name, or (as in Resource.validate_external()) we will get an assertion error. To simplify the avoidance of programming errors, define a _default_client_plugin() method that *always* returns a plugin whose is_not_found() and is_conflict() methods can be called. Change-Id: I1005397187457d9be42ba86096644dd17287d0e7 Story: #1745024 Task: 17677		2018-06-18 16:41:43 -04:00
..
__init__.py	Change namespace for Manila tests	2015-11-20 12:38:08 +08:00
test_security_service.py	Begin move of UpdateReplace back to its rightful location	2016-08-18 12:57:54 -04:00
test_share.py	Use correct raw string format	2017-11-16 18:23:58 -05:00
test_share_network.py	Handle resource plugins without default_client_name	2018-06-18 16:41:43 -04:00
test_share_type.py	manila resources observe reality implementation	2017-02-10 13:24:28 +04:00