-
Notifications
You must be signed in to change notification settings - Fork 172
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
Landing page - Packages #1311
Milestone
Comments
An endpoint exists for cluster information but will need the following information added:
An endpoint exists to list packages. No endpoint exists for resources - resources will be hardcoded as No endpoint exists to return all of the kubecontexts - this endpoint will need to be created. |
mike-winberry
added a commit
that referenced
this issue
Mar 30, 2023
…ost to the ClusterSummary. Update types/api.go ClusterSummary to have the Host field. Updated the navdrawer to have the cluster type and host under the Cluster section. Update route/+layout to retrieve clusterSummary. Add back in the error page
mike-winberry
added a commit
that referenced
this issue
Mar 30, 2023
mike-winberry
added a commit
that referenced
this issue
Apr 5, 2023
… found and when no packages exist. Created the cluster-table and no cluster connected states
mike-winberry
added a commit
that referenced
this issue
Apr 5, 2023
mike-winberry
added a commit
that referenced
this issue
Apr 5, 2023
…ks only for init package in cwd.
mike-winberry
added a commit
that referenced
this issue
Apr 6, 2023
…ternal ambient types. Update svelte kit version to fix high severity vulnerability. Update find.go regexes to search for all init packages and to recurse through the homedirectory searching for init and zarf-packages. Update local-package-table to use the findInHome instead of find (which searches the cwd). added back in the previous package deploy step pages and updated theming. ZarfUI can now find and deploy packages.
mike-winberry
added a commit
that referenced
this issue
Apr 6, 2023
…nd to get the User, ClusterName and all contexts for future context switching.
mike-winberry
added a commit
that referenced
this issue
Apr 7, 2023
…. Update local-package-table to use findInHome instead of find. Update nav-drawer by refactoring out ssx in subcomponent to ssx var using a class
mike-winberry
added a commit
that referenced
this issue
Apr 8, 2023
…te deploy package page terminal with color from design
mike-winberry
added a commit
that referenced
this issue
Apr 8, 2023
mike-winberry
added a commit
that referenced
this issue
Apr 11, 2023
mike-winberry
added a commit
that referenced
this issue
Apr 11, 2023
Merged
Racer159
added a commit
that referenced
this issue
Apr 18, 2023
## Description Fixes: #1500 Fixes: #1311 ## Closes Fixes: #964 Fixes: #807 Fixes: #794 Fixes: #1500 Fixes: #1311 --------- Co-authored-by: Jessy-Morris <[email protected]> Co-authored-by: Wayne Starr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Big Components
*Ignore - signed stuff
As Ashton I want to be able to connect to a cluster and deploy packages so that I can setup services that my organization needs.
Connec/Initialize Zarf Cluster UX Flow
Connect a Cluster (Kubeconfig available)
Given - the user does not have a cluster connected (initialized with Zarf)
Then - show connect cluster button and disable the deploy package button
When - the user clicks connect cluster
Then - scan kubeconfig for available contexts
And - show a modal that lists the default cluster default (radio button to selected state)
If - User clicks Connect cluster - start to deploy wizard
If - User clicks cancel - return to the main screen. (Packages)
Connect a Cluster (No Kubeconfig)
Given - the user does not have a cluster connected (initialized with Zarf)
Then - show connect cluster button and disable the deploy package button
When - the user clicks connect cluster
Then - scan kubeconfig for available contexts
If - on Linux show a dialog with a button to deploy the init-package (to install k3s)
when - the user clicks deploy init
Then - start to deploy wizard
If - not on linux show a dialog message explaining user needs to create or connect to a cluster to connect.
Initialize a Cluster
Given - the user has a cluster connected
When - a user clicks initialize cluster button
Then - they will be directed to step one of the deploy modal (select package)
And - the user should only see init packages (filter by Zarfinitconfig package type)
When - a user selects the init package
Then - they will be taken through the rest of the deploy flow
... deploy flow
When - the user has deployed the init package
Then - (if failed) stay on deployed page
And - show the error page and recommend user to go to the CLI to get logs
Then - (if successful) show success dialog
Then - redirect to package page (default)
And - Show Cluster Context and details
And - show deployed package is added to package table
And - deploy button is now active
Deploy Zarf Package
Deploy Package
Given - a user has clicked the deploy package button
Then - they will be directed to step one of the deploy modal (select package)
And - then should only see all packages
When - a user selects the package they will be taken through the deploy flow
... deploy flow
When - the user has deployed the package
Then - (if failed) stay on deployed page
And - show the error page and recommend user to go to the CLI to get logs
Then - (if successful) show success
And - redirect the user to the main page where deployed package is added to package table with link to tunnel if needed
Design File
https://www.figma.com/file/MUItIzpzLBLuIyt225Bwgl/Zarf-UI?node-id=1081%3A54952&t=ojULNeuu0CxY2PM1-1
The text was updated successfully, but these errors were encountered: