AMBARI-26634: Advance React parity for remaining frontend refactor modules - #4176
Merged
Conversation
zRains
approved these changes
Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue: AMBARI-26634
What changes were proposed in this pull request?
Complete the remaining non-Metrics React parity work across ResourceManager and Ranger Admin HA, Federation and HAWQ workflows, Views, global authorization and feature gates, and server-driven Service Theme layouts.
The implementation adds guarded routes and actions, durable long-running workflow checkpoints and recovery, exact configuration and API handling, View-only shell behavior, operational log counts, stack and permission policies, Theme parsing/rendering/Widget behavior across four consumers, and server Theme provider contract fixes.
The history is split into 20 topic commits so shared infrastructure, each HA workflow, Views, each Theme integration layer, the server provider, parity evidence, and review guidance can be reviewed independently. The baseline and React gap documents record the remaining real-cluster validation and server-protocol boundaries instead of claiming static parity for those cases.
How was this patch tested?
ThemeArtifactResourceProviderTest: 14 tests passed.git diff --check origin/frontend-refactor..HEADpassed.Existing non-blocking warnings remain: Vitest
TimeoutNaNWarning, Sass deprecations, excluded Metricsevalwarnings, and Vite large-chunk warnings. Full-project ESLint remains outside this patch because the branch contains longstanding lint debt.Please review Ambari Contributing Guide before opening a pull request.