| Ghanshyam Mann | 35fc95d | 2023-01-18 23:22:29 -0600 | [diff] [blame] | 1 | --- |
| 2 | fixes: |
| 3 | - | |
| 4 | There was a bug (bug#1964509) in dynamic credentials creation where |
| 5 | project credentials with different roles are created with the new |
| 6 | projects. Credential of different role of projects must be created |
| 7 | within the same project. For exmaple, 'project_admin', 'project_member', |
| 8 | 'project_reader', and 'primary', credentials will be created in the |
| 9 | same projects. 'alt', 'project_alt_admin', 'project_alt_member', |
| 10 | 'project_alt_reader' will be created within the same project. |
| 11 | |
| 12 | 'admin' credenatials is considered and kept as legacy admin and |
| 13 | will be created under new project. If any test want to test with |
| 14 | admin role in projectA and non-admin/admin in projectB then test |
| 15 | can request projectA admin using 'admin' or 'project_alt_admin' |
| 16 | and non-admin in projectB using 'primary', 'project_member', |
| 17 | or 'project_reader'/admin in projectB using 'project_admin'. Many |
| 18 | existing tests using the 'admin' with new project to assert on the |
| 19 | resource list so we are keeping 'admin' a kind of legacy admin. |