b757001456
Updated scores for existing capabilities. identity-v3-validate-token but it is admin only. Change-Id: I111aecf36eae125126cb27bfc4c69bd1dbd2fa9a
3.8 KiB
3.8 KiB
1 | Capability | Program | Status | Method | Endpoint | Test available? | interop relevant? | PTL Comments | From Defcore Discussion | Scorer Comments | |
---|---|---|---|---|---|---|---|---|---|---|---|
2 | identity-v3-api-discovery | platform/compute | required | 3 | yes | make required | tempest.api.identity.v3.test_api_discovery{test_api_version_resources, test_api_media_types, test_api_version_statuses} | ||||
3 | identity-v3-list-projects | platform/compute | advisory | GET | /v3/users/{user_id}/projects | 1 | yes | ||||
4 | |||||||||||
5 | identity-v3-create-ec2-credentials | POST | /v3/credentials | 1 | yes | Should we make ec2 compatibility required? unclear | |||||
6 | identity-v3-list-ec2-credentials | GET | /v3/credentials | 1 | yes | Should we make ec2 compatibility required? unclear | |||||
7 | identity-v3-show-ec2-credentials | GET | /v3/credentials/{credential_id} | 1 | yes | Should we make ec2 compatibility required? unclear | |||||
8 | identity-v3-delete-ec2-credentials | DELETE | /v3/credentials/{credential_id} | 1 | yes | Should we make ec2 compatibility required? unclear | |||||
9 | identity-v3-update-ec2-credentials | PATCH | /v3/credentials/{credential_id} | Should we make ec2 compatibility required? unclear | |||||||
10 | identity-v3-catalog | (make sure it works on all supported releases) | returned with the token | ||||||||
11 | identity-v3-password-update | POST | /v3/users/{user_id}/password | 1 | yes | Untestable without changing user's password, security risk. Also password policies are very particular to different companies, making a test that would pass on all is near impossible. | tempest.api.identity.v3.test_users{test_update_own_password} | ||||
12 | |||||||||||
13 | identity-v3-list-groups | platform/compute | GET | /v3/users/{user_id}/groups | 0 | yes | no test available for this feature | ||||
14 | identity-v3-get-project | platform/compute | GET | /v3/projects/{project_id} | 0 | yes | admin required | ||||
15 | identity-v3-list-roles | platform/compute | GET | /v3/roles | 0 | no | admin required | ||||
16 | identity-v3-get-role | platform/compute | GET | /v3/roles/{role_id} | no | admin required | |||||
17 | identity-v3-list-domains | platform/compute | GET | /v3/domains | no | admin required | |||||
18 | identity-v3-get-domain | platform/compute | GET | /v3/domains/{domain_id} | no | admin required | |||||
19 | |||||||||||
20 | identity-v3-validate-token | platform/compute | GET | /v3/auth/tokens | yes | Token to be validated is passed in the X-Subject-Token header | This sounds backwards to me, need to check with steve, shouldn't it be POST for validating and GET for getting a token? | ||||
21 | identity-v3-revoke-token | platform/compute | DELETE | /v3/auth/tokens | 1 | yes | Token to be revoked is passed in the X-Subject-Token header | keystone.keystone.tests.unit.test_revoke{test_revoke_by_user} | |||
22 | identity-v3-get-catalog | platform/compute/object | GET | /v3/auth/catalog | 0 | yes | couldn't find a test specific for this, there are some tests related in keystone.tests.unit.test_v3_auth.py | ||||
23 | identity-v3-get-auth-projects | platform/compute | GET | /v3/auth/projects | 0 | yes | equivalent as far as I can tell to identity-v3-list-projects. couldn't find a test specific for this, there are some tests related in keystone.tests.unit.test_v3_auth.py | ||||
24 | |||||||||||
25 | identity-v2-list-versions | GET | / | 1 | yes | Deprecated | |||||
26 | identity-v2-show-version | GET | /v2.0 | 1 | yes | Deprecated | |||||
27 | identity-v2-token-generation | POST | /v2.0/tokens | 1 | yes | Deprecated | |||||
28 | identity-v2-tenants | GET | /v2.0/tenants | 1 | yes | Deprecated | |||||
29 | identity-v2-list-extensions | GET | /v2.0/extensions | Deprecated | |||||||
30 | identity-v2-show-extension | GET | /v2.0/extensions/{alias} | Deprecated |