Skip to content

Refactoring of the project creation component to enable domain, account, and user specification#12646

Open
erikbocks wants to merge 1 commit intoapache:4.20from
scclouds:add-ownership-selection-to-project-creation
Open

Refactoring of the project creation component to enable domain, account, and user specification#12646
erikbocks wants to merge 1 commit intoapache:4.20from
scclouds:add-ownership-selection-to-project-creation

Conversation

@erikbocks
Copy link
Copy Markdown
Collaborator

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

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Screenshots (if appropriate):

image
Projects created with the new form image

How Has This Been Tested?

First, the subdomain domain was created, the normalroot account was created in the ROOT domain, and the subdomainuser account was created in the subdomain domain. The subDomainAnotherUser user was also created in the subdomainuser account. Then, using the new project creation component, I created the following projects:

  • Project in the ROOT domain with the admin account as the owner;
  • Project in the ROOT domain with the normalroot account as the owner;
  • Project in the subdomain domain with the subdomainuser account as the owner;
  • Project in the subdomain domain with the subDomainAnotherUser user from the subdomainuser account 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 OwnershipSelection component (VM deployment, VM assignment and Guest Network creation) were not affected by the changes.

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 16.26%. Comparing base (8eb162c) to head (7c7776a).

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              
Flag Coverage Δ
uitests 4.15% <ø> (-0.01%) ⬇️
unittests 17.11% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sureshanaparti
Copy link
Copy Markdown
Contributor

@blueorangutan package

@blueorangutan
Copy link
Copy Markdown

@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.

@blueorangutan
Copy link
Copy Markdown

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 16839

@winterhazel
Copy link
Copy Markdown
Member

@erikbocks as this is a simple enhancement, could you target the next 4.20/4.22 minor?

@DaanHoogland
Copy link
Copy Markdown
Contributor

@blueorangutan ui

@blueorangutan
Copy link
Copy Markdown

@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@erikbocks erikbocks changed the base branch from main to 4.20 April 14, 2026 19:37
@erikbocks erikbocks force-pushed the add-ownership-selection-to-project-creation branch from 84f3cfa to 7c7776a Compare April 14, 2026 19:37
@erikbocks erikbocks requested a review from winterhazel April 14, 2026 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants