New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: initial new enclave manager #1603
Conversation
One more thing: can you add a build script (put it under |
Thanks for the extra comments and chatting last night @adschwartz . I've updated this PR with all of the feedback we discussed to change now. I'm going to go through the design changes now in a fresh branch from this one. |
## Description: This PR primarily adds support for the new enclave view to the enclave manager, and picks up changes to the design of components. Significant changes: * The enclave view is added * Theming has been updated to match the mocks. Now that I've taken a few look over the mocks and am more familiar with which components are special and which are common, where possible I've shifted to overriding existing chakra styles rather than defining new ones for the brand * The breadcrumb logic will now be used across the application, rather than custom for enclaves (catalog etc) * React router is used properly to load data, rather than loading in effects. In order to provide the `kurtosisClient` to react router - which can only be provided after initial render - the `createBrowserRouter` is moved around a little to live inside the new `KurtosisRouteProvider` instead. ### Feedback required: * The mocks include container started times. I think the api needs to have this added * The mocks include file descriptions - is this actually stored? How can it be obtained * The port summary overview is not in the mocks - my implementation is likely poorly designed. * Is there an empty state for tables that can be used? ### Demo https://github.com/kurtosis-tech/kurtosis/assets/4419574/192240bd-6cbf-4a69-9c7f-072783fd965e ## Is this change user facing? NO (This is not yet in the deploy process) ## References (if applicable): This PR is based on top of #1603 which should be merged first. --------- Co-authored-by: Anders Schwartz <anders.schwartz@kurtosistech.com>
🤖 I have created a release *beep* *boop* --- ## [0.85.1](0.85.0...0.85.1) (2023-10-31) ### Features * initial new enclave manager ([#1603](#1603)) ([9944658](9944658)) * warn users of diff architecture image running ([#1649](#1649)) ([77f2f69](77f2f69)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: kurtosisbot <kurtosisbot@users.noreply.github.com>
Description:
This PR contains the beginnings of the new enclave manager ui. Specifically it adds a new project in
enclave-manager/web
. Notable inclusions:useKurtosisClient
by theKurtosisClientProvider
. This provider blocks loading the application (with a spinner) until it's configured the client to use.Demo (WIP)
kurtosisBones.mp4
Is this change user facing?
NO (this is not yet part of the build/deploy process)
References (if applicable):
This PR is rebased on top of #1595 which should be merged first.