blob: 26282f0adbdc7cd34460549e79d758ebccad45d5 [file] [log] [blame]
Ghanshyam Mann2d0da042021-03-05 09:09:30 -06001---
2features:
3 - |
4 Dynamic credentials now support the scope type for specific roles
5 too along with ``admin``, ``member``, ``reader`` role.
6 Test can specify the scope in the prefix of ``cls.credentials`` name.
7 If ``system`` is prefix in ``cls.credentials`` name then creds will
8 be created with scope as ``system``. If ``domain`` is prefix in
9 ``cls.credentials`` name then creds will be created with scope as
10 ``domain`` otherwise default ``project`` scope will be used.
11 For Example::
12
13 credentials = [['my_role', 'role1'], # this will be old style and project scoped
14 ['project_my_role', 'role1'], # this will be project scoped
15 ['domain_my_role', 'role1'], # this will be domain scoped
16 ['system_my_role', 'role1']] # this will be system scoped
17
18 And below is how test can access the credential manager of respective
19 credentials type::
20
21 cls.os_my_role.any_client
22 cls.os_project_my_role.any_client
23 cls.os_domain_my_role.any_client
24 cls.os_system_my_role.any_client
25
26
27 For backward compatibility, we set the credentials manager class attribute
28 in old style form too which is prefix with ``os_roles_*``, example
29 ``cls.os_roles_my_role`` but we recommend to use the new style attribute
30 as shown above.
31issues:
32 - |
33 Scope support for specific role is not yet added for pre-provisioned credentials.
34fixes:
35 - |
36 Fixes the `bug# 1917168 <https://bugs.launchpad.net/tempest/+bug/1917168>`_