JiaLiangC opened a new pull request, #4179: URL: https://github.com/apache/ambari/pull/4179
Issue: [AMBARI-26634](https://issues.apache.org/jira/browse/AMBARI-26634) ## What changes were proposed in this pull request? This pull request advances the React frontend toward behavioral parity with the legacy Ember application, excluding Metrics scope. It completes the shared Service Theme layout and configuration editing path across installed services, hosts, configuration comparison, Installer, and Add Service flows. The Theme engine now preserves full configuration identity, grid placement, conditions, widgets, permissions, config-group overrides, save payloads, fallback, retry, and stale-response recovery while keeping categorized wizard Themes out of installed-service pages as Ember does. It also fixes runtime crashes in configuration history and background command rendering, restores request and authentication contracts, stabilizes application initialization and refresh state, and makes Add Service cancellation reliably release persisted wizard state and return to the originating service page. The server changes harden HTTP method override request bodies and inherited Theme merging, including null-safe child additions, removals, declaration ordering, and parent-object isolation. The frontend baseline and React parity evidence were updated from the verified Ember source and regenerated with the repository tools. ## How was this patch tested? The aggregate React suite passed with 187 test files and 986 tests. The Vite production build completed successfully. Both frontend baseline validators passed with 1,154 canonical feature IDs and synchronized JSON, CSV, and Markdown evidence. The focused server Theme suite passed 21 tests: 2 Theme merge tests, 5 Theme module tests, and 14 Theme resource-provider tests. Playwright drove a real Chrome session against the three-node ZooKeeper cluster at `127.0.0.1:8080`. It verified installed-service configuration rendering, expanded `Advanced zoo.cfg`, and Add Service cancellation back to ZooKeeper Summary with no page errors. The only failed response was the deployment's optional, unconfigured MOTD endpoint (`GET /api/v1/settings/motd`, HTTP 404). ```shell (cd ambari-web/latest && npm test -- --run)\n(cd ambari-web/latest && npm run build)\nnode docs/frontend-refactor/ember-baseline/tools/validate-ember-baseline.mjs\nnode docs/frontend-refactor/react-current/tools/validate-react-parity-matrix.mjs\ndocker run --rm -v "$PWD":/workspace -w /workspace maven:3.9.11-eclipse-temurin-17 mvn -pl ambari-server -Dtest=ThemeMergeTest,ThemeModuleTest,ThemeArtifactResourceProviderTest -Dcheckstyle.skip -Drat.skip=true -DskipPythonTests test\ngit diff --check ``` **ZooKeeper installed-service configuration rendering (categorized wizard Themes excluded):**\n\n **Expanded Advanced zoo.cfg rendering:**\n\n **Add Service cancellation returned to ZooKeeper Summary:**\n\n 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]
