interop/working_materials/keystone_capabilities_info.csv

3.8 KiB

1CapabilityProgramStatusMethodEndpointTest available?interop relevant?PTL CommentsFrom Defcore DiscussionScorer Comments
2identity-v3-api-discoveryplatform/computerequired3yesmake requiredtempest.api.identity.v3.test_api_discovery{test_api_version_resources, test_api_media_types, test_api_version_statuses}
3identity-v3-list-projectsplatform/computeadvisoryGET/v3/users/{user_id}/projects1yes
4
5identity-v3-create-ec2-credentialsPOST/v3/credentials1yesShould we make ec2 compatibility required? unclear
6identity-v3-list-ec2-credentialsGET/v3/credentials1yesShould we make ec2 compatibility required? unclear
7identity-v3-show-ec2-credentialsGET/v3/credentials/{credential_id}1yesShould we make ec2 compatibility required? unclear
8identity-v3-delete-ec2-credentialsDELETE/v3/credentials/{credential_id}1yesShould we make ec2 compatibility required? unclear
9identity-v3-update-ec2-credentialsPATCH/v3/credentials/{credential_id}Should we make ec2 compatibility required? unclear
10identity-v3-catalog(make sure it works on all supported releases)returned with the token
11identity-v3-password-updatePOST/v3/users/{user_id}/password1yes 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
13identity-v3-list-groupsplatform/computeGET/v3/users/{user_id}/groups0yesno test available for this feature
14identity-v3-get-projectplatform/computeGET/v3/projects/{project_id}0yesadmin required
15identity-v3-list-rolesplatform/computeGET/v3/roles0noadmin required
16identity-v3-get-roleplatform/computeGET/v3/roles/{role_id}noadmin required
17identity-v3-list-domainsplatform/computeGET/v3/domainsnoadmin required
18identity-v3-get-domainplatform/computeGET/v3/domains/{domain_id}noadmin required
19
20identity-v3-tokens-validateplatform/computeGET/v3/auth/tokensyesToken to be validated is passed in the X-Subject-Token headerThis sounds backwards to me, need to check with steve, shouldn't it be POST for validating and GET for getting a token?
21identity-v3-revoke-tokenplatform/computeDELETE/v3/auth/tokens1yesToken to be revoked is passed in the X-Subject-Token headerkeystone.keystone.tests.unit.test_revoke{test_revoke_by_user}
22identity-v3-get-catalogplatform/compute/objectGET/v3/auth/catalog0yescouldn't find a test specific for this, there are some tests related in keystone.tests.unit.test_v3_auth.py
23identity-v3-get-auth-projectsplatform/computeGET/v3/auth/projects0yesequivalent 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
25identity-v2-list-versionsGET/1yesDeprecated
26identity-v2-show-versionGET/v2.01yesDeprecated
27identity-v2-token-generationPOST/v2.0/tokens1yesDeprecated
28identity-v2-tenantsGET/v2.0/tenants1yesDeprecated
29identity-v2-list-extensionsGET/v2.0/extensionsDeprecated
30identity-v2-show-extensionGET/v2.0/extensions/{alias}Deprecated