Sergey Kraynev d204c979b8 Don't use default None for params in handle_update ... The main "update" function in resource.py call custom handle_update methods of resources. handle_update method always get not None parameters: after, tmpl_diff, prop_diff. Where: - 'after' is not None snippet of resource - tmpl_diff and prop_diff - values calculated corresponding functions, which return only dictionary (empty or not empty). This patch removes default None values from handle_update method of some resources to make all interfaces similar. Change-Id: Id62201e3a26b557a941bbd904a947f064df4aeb3		2015-08-07 04:42:33 -04:00
..
__init__.py	Move keystone resources in-tree	2015-06-01 09:50:46 -07:00
endpoint.py	Don't use default None for params in handle_update	2015-08-07 04:42:33 -04:00
group.py	Don't use default None for params in handle_update	2015-08-07 04:42:33 -04:00
project.py	Don't use default None for params in handle_update	2015-08-07 04:42:33 -04:00
role.py	Don't use default None for params in handle_update	2015-08-07 04:42:33 -04:00
role_assignments.py	Use default_client_name for keystone	2015-07-21 17:24:33 +03:00
service.py	Don't use default None for params in handle_update	2015-08-07 04:42:33 -04:00
user.py	Don't use default None for params in handle_update	2015-08-07 04:42:33 -04:00