Sandeep Kumar created AMBARI-26660:
--------------------------------------

             Summary: Align React UI Config Theme handling with emberjs
                 Key: AMBARI-26660
                 URL: https://issues.apache.org/jira/browse/AMBARI-26660
             Project: Ambari
          Issue Type: Story
            Reporter: Sandeep Kumar
            Assignee: Sandeep Kumar


Customize Services (installer Step 7 → ALL CONFIGURATIONS), ambari-web/latest.

RANGER_KMS declares two default Theme artifacts, theme_version_1.json 
(db_settings, kms_hsm) and theme_version_2.json (kms_keysecure). Classic's 
mapper accumulates the tabs, placements and widgets of every artifact; 
normalizeThemeResponse keeps the first and reports the rest as duplicates, so 
the Ranger KMS KeySecure tab never renders. With those configs unplaced, the 
subsection condition on dbks-site/ranger.kms.keysecure.enabled can no longer 
hide them, so seven empty dbks-site KeySecure properties show "This is 
required" in Advanced and block the wizard while KeySecure is disabled.

Two banners also report metadata classic tolerates silently: Theme conditions 
referencing configs the stack does not define (ranger-env/bind_anonymous, the 
Atlas tagsync configs — already ignored at evaluation time, matching classic), 
and services that ship no default Theme at all (TEZ, ZOOKEEPER, which correctly 
fall back to the generated Advanced tab).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to