JiaLiangC opened a new pull request, #4174:
URL: https://github.com/apache/ambari/pull/4174

   Issue: [AMBARI-26632](https://issues.apache.org/jira/browse/AMBARI-26632)
   
   ## What changes were proposed in this pull request?
   
   Completes the non-Metrics React Kerberos module against all 81 legacy Ember 
baseline feature IDs. This implements the permission and feature gates, 
MIT/AD/IPA/Manual mode behavior, ordered wizard operations, persisted request 
recovery, Stack Advisor and descriptor handling, enable/disable cleanup and 
retry paths, credential management, identity editing, and keytab regeneration. 
Focused tests and the React comparison evidence cover success, failure, retry, 
reload, and compatibility-correction paths; real-cluster and cross-module 
boundaries remain explicitly documented.
   
   ## How was this patch tested?
   
   Passed: 67 frontend test files and 251 tests; the Vite production build; the 
Ember baseline validator with 1,002 IDs and no warnings or errors; 16 ambari-ai 
helper unit tests; and git diff --check. Repository-wide ESLint still reports 
pre-existing debt, while this branch reduces the clean-base total from 6,315 
findings to 6,298.
   
   ```shell
   cd ambari-web/latest && npm test
   cd ambari-web/latest && npm run build
   node docs/frontend-refactor/ember-baseline/tools/validate-ember-baseline.mjs
   (cd dev-support/ambari-ai && python3 -m unittest -v)
   git diff --check
   ```
   
   Please review [Ambari Contributing 
Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) 
before opening a pull request.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to