Skip to content

Conversation

Pearl1594
Copy link
Contributor

Description

This PR fixes #11570
Following issues were fixed:

  1. When updating domain-level setting (from UI) it is observed that it doesn't pass the domain id, hence leading to the update of the global setting
  2. On switching between different domains, the settings weren't getting updated. i.e., while the API returns the correct value, the settings displayed the older domains values.

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

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

Copy link

codecov bot commented Sep 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 17.36%. Comparing base (3d6ec29) to head (2ab54d9).

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #11571      +/-   ##
============================================
- Coverage     17.36%   17.36%   -0.01%     
  Complexity    15237    15237              
============================================
  Files          5888     5888              
  Lines        525741   525746       +5     
  Branches      64164    64167       +3     
============================================
- Hits          91274    91273       -1     
- Misses       424167   424172       +5     
- Partials      10300    10301       +1     
Flag Coverage Δ
uitests 3.63% <ø> (-0.01%) ⬇️
unittests 18.40% <ø> (-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.

@weizhouapache weizhouapache added this to the 4.20.2 milestone Sep 3, 2025
Copy link

sonarqubecloud bot commented Sep 3, 2025

@shwstppr
Copy link
Contributor

shwstppr commented Sep 4, 2025

@blueorangutan ui

@blueorangutan
Copy link

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

@blueorangutan
Copy link

UI build: ✔️
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/11571 (QA-JID-737)

Copy link
Contributor

@harikrishna-patnala harikrishna-patnala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Pearl1594 does this need change in base branch to 4.20 ?

@@ -280,6 +295,9 @@ export default {
name: configrecord.name,
value: newValue
}
if (this.scopeKey === 'domainid' && !params[this.scopeKey]) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need the this.scopeKey === 'domainid' check? Can it be

Suggested change
if (this.scopeKey === 'domainid' && !params[this.scopeKey]) {
if (this.scopeKey && !params[this.scopeKey]) {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I specifically added domainid, because it's taken care of for other cases.

@@ -254,6 +258,17 @@ export default {
this.setConfigData()
},
watch: {
loading (newVal, oldVal) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is loading value for the element set somewhere in the code?
Similarly for property configDisable, though unrelated to the PR

@bernardodemarco bernardodemarco self-requested a review September 4, 2025 11:39
@weizhouapache weizhouapache self-assigned this Sep 10, 2025
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.

ldap.search.group.principle Issue
5 participants