Repository navigation
Add the control plane console - #5863
bhagyasakalanka wants to merge 2 commits into
Conversation
|
Important Review skippedToo many files! This PR contains 170 files, which is 20 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configuration
⛔ Files ignored due to path filters: 1
📒 Files selected for processing: 170
You can disable this status message by setting the
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
d2523f9 to
f3f2829
Compare
|
@coderabbitai review |
|
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
8023a2a to
e1028eb
Compare
Signed-off-by: bhagyasakalanka <bsakalanka9@gmail.com>
Signed-off-by: bhagyasakalanka <bsakalanka9@gmail.com>
e1028eb to
265836b
Compare
Purpose
The control plane administers the gateways configuration is deployed to (#5602), and it executes no flows. Its console therefore needs gateway management, and the administration operations the console runs through a flow on the all-in-one server have to call the management API directly.
Rather than one console build that switches on a runtime flag, this adds a console app for the control plane,
frontend/apps/console-cp, composed from the same feature packages as the console plus gateway management (#5716), with every administration operation running natively (#5559). Which features a console has is decided by what each app mounts, not by a setting every package reads.Approach
@thunderid/configure-onboarding, a new package, holds what the console previously implemented itself and both consoles need: the home page and its cards, the welcome page, Create Project, Get Started and the three tryouts, with the quick start bundle import. The pages read their routes throughuseOnboardingRoutesand the host'sRoutesProvider, like every feature package; the bundles the build stages into an app are handed down throughSampleBundlesProvider. The console mounts the package where its own pages were, and its tests moved with the code (they now run in Chromium, as package tests do).WelcomePagetakestryouts={false}for a host that offers no tryouts.frontend/apps/console-cpis the console the control plane serves at/console: the console's shell (layouts, HOCs, i18n, route table) with/gateways,/gateways/{id}) in the navigation, from@thunderid/configure-gateways.AdministrationProviderwith modenativearound the whole app, so user and application deletion and secret regeneration call the API directly, and so will user and agent creation once Add users and agents natively when the console runs without flows #5703 lands.publicfolder (icons, favicons,config.js) through Vite'spublicDirrather than a copy, since nothing in it is specific to a plane; the control plane gets its own when it gets its own distribution.The console app itself changes only by taking the onboarding pages from the package.
Packaging follows separately. The control plane has no distribution of its own yet, so
build.shkeeps packingapps/console; when the control plane distribution is set up, it builds and packsapps/console-cp, stages the quick start bundles into it, and the control plane server serves that folder. Untilpr-builder.ymllists the new app, its tests run locally but not in CI; the onboarding package's tests run with the other packages.Related Issues
Related PRs
Checklist
Security checks
🤖 Generated with Claude Code