Refactoring of the project creation component to enable domain, account, and user specification#12646
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.20 #12646 +/- ##
============================================
- Coverage 16.26% 16.26% -0.01%
Complexity 13433 13433
============================================
Files 5665 5666 +1
Lines 500530 500565 +35
Branches 60787 60791 +4
============================================
- Hits 81411 81410 -1
- Misses 410027 410063 +36
Partials 9092 9092
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 16839 |
|
@erikbocks as this is a simple enhancement, could you target the next 4.20/4.22 minor? |
|
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
…nt, and user specification
84f3cfa to
7c7776a
Compare
Description
Currently, it is not possible to specify in the GUI which domain that the project will be created in, neither the account or the user that will be assigned as the project owner, automatically assigning the project to the current user. The project creation component was refactored to allow the specification of the domain, account or user of the project during the project creation.
The current user's account and domain are automatically selected. If the current user does not belong to the selected domain, the first account returned in the listing is selected.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
Projects created with the new form
How Has This Been Tested?
First, the
subdomaindomain was created, thenormalrootaccount was created in theROOTdomain, and thesubdomainuseraccount was created in thesubdomaindomain. ThesubDomainAnotherUseruser was also created in thesubdomainuseraccount. Then, using the new project creation component, I created the following projects:ROOTdomain with theadminaccount as the owner;ROOTdomain with thenormalrootaccount as the owner;subdomaindomain with thesubdomainuseraccount as the owner;subdomaindomain with thesubDomainAnotherUseruser from thesubdomainuseraccount as the owner.Logged in as a normal user, I validated that the ownership selection component was not shown, and when the project was created, it was automatically assigned to the current account.
I also validated that other features flows that use the
OwnershipSelectioncomponent (VM deployment, VM assignment and Guest Network creation) were not affected by the changes.