-
Notifications
You must be signed in to change notification settings - Fork 171
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
Improve package selection Web UI workflow #1665
Comments
… update FindInitPackage to use the version name and to look in execution, cache directory, and the current working directory. Update io.go with a FileList method that reads a directory and returns a list of filepaths matched against an optional regex.
…er for packages with the /packages/explore route.
@Racer159 - I updated this issue to discuss a new UX flow for searching for zarf packages. I changed a few things:
|
Not sure I agree with showing all init packages since that may be more dangerous then helpful - we pair them together because the init package contains the Zarf agent which can have breaking changes between versions and might break a cluster deployment in weird ways that would be hard to debug. |
Is that a current behavior in the CLI as well? |
Design is finalized and ready in Figma |
…ts as they are found and open a dialog if not. TODO add recursive file streaming and the expanded search.
…query param init: boolean and recursively streams packages from the users home folder (init packages when init = true). Update utils io.go with IsTrashBin method that takes in a directory path and checks if it is the os trash bin. Updat the ui server with new packages/find/stream routes. Update frontend api with new routes and method for recursively streaming packages. TODO: add the expanded search button and logic.. Handle warnings for init packages that dont match the executable version.
…eList; Extracted hidded directory check into IsHidden utility method; Removed unused FileList method. Update all references to RecursiveFileList references to nolonger have the unused flags. Update api/packages find.go: Removed the initPackagesPattern and replaced references with currentInitPattern; Update recursivePackageStream to ignore hidden directories as well as the Trash folder.
…rch again after expanded search has been run.
…eList; Extracted hidded directory check into IsHidden utility method; Removed unused FileList method. Update all references to RecursiveFileList references to nolonger have the unused flags. Update api/packages find.go: Removed the initPackagesPattern and replaced references with currentInitPattern; Update recursivePackageStream to ignore hidden directories as well as the Trash folder.
…rch again after expanded search has been run.
… update FindInitPackage to use the version name and to look in execution, cache directory, and the current working directory. Update io.go with a FileList method that reads a directory and returns a list of filepaths matched against an optional regex.
…er for packages with the /packages/explore route.
…ts as they are found and open a dialog if not. TODO add recursive file streaming and the expanded search.
…query param init: boolean and recursively streams packages from the users home folder (init packages when init = true). Update utils io.go with IsTrashBin method that takes in a directory path and checks if it is the os trash bin. Updat the ui server with new packages/find/stream routes. Update frontend api with new routes and method for recursively streaming packages. TODO: add the expanded search button and logic.. Handle warnings for init packages that dont match the executable version.
…eList; Extracted hidded directory check into IsHidden utility method; Removed unused FileList method. Update all references to RecursiveFileList references to nolonger have the unused flags. Update api/packages find.go: Removed the initPackagesPattern and replaced references with currentInitPattern; Update recursivePackageStream to ignore hidden directories as well as the Trash folder.
…rch again after expanded search has been run.
… update FindInitPackage to use the version name and to look in execution, cache directory, and the current working directory. Update io.go with a FileList method that reads a directory and returns a list of filepaths matched against an optional regex.
…er for packages with the /packages/explore route.
…ts as they are found and open a dialog if not. TODO add recursive file streaming and the expanded search.
…query param init: boolean and recursively streams packages from the users home folder (init packages when init = true). Update utils io.go with IsTrashBin method that takes in a directory path and checks if it is the os trash bin. Updat the ui server with new packages/find/stream routes. Update frontend api with new routes and method for recursively streaming packages. TODO: add the expanded search button and logic.. Handle warnings for init packages that dont match the executable version.
…eList; Extracted hidded directory check into IsHidden utility method; Removed unused FileList method. Update all references to RecursiveFileList references to nolonger have the unused flags. Update api/packages find.go: Removed the initPackagesPattern and replaced references with currentInitPattern; Update recursivePackageStream to ignore hidden directories as well as the Trash folder.
…rch again after expanded search has been run.
## Is your feature request related to a problem? Please describe. Our package selection workflow in the UI is a bit slow due to searching the entire home directory at one time. ## Describe the solution you'd like Recommend the following changes: ### For 'init' package deployment - [x] in the selection window, only show init packages that exist in the three places that Zarf searches for them: - Current Working Directory - Zarf Binary Directory - Home `.zarf-cache` folder - Only show init packages that match the current build version. ### Regular Package Deployment For 'regular' packages - the UX flow proceeds in two parts: - [x] Search # 1. - Search and show packages located in the current working directory w/o subdirectories (matching the tab behavior on `zarf package deploy`) - If packages are found show in the table and add a expand search button to table that executes search # 2 - If no packages are found - show no package found error message (gives the user option to cancel deployment or proceed to part # 2 - [x] search part # 2 - Search and show packages located in the entire home directory - Exclude trash - Exclude hidden folders - [x] For both workflows, increase the height of the package selection table to show more packages at once ## Design File https://www.figma.com/file/MUItIzpzLBLuIyt225Bwgl/Zarf-Web-Ui?type=design&node-id=1544%3A56348&t=JeB5xVvOb7lcP6ZB-1 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) --------- Co-authored-by: Wayne Starr <[email protected]>
Is your feature request related to a problem? Please describe.
Our package selection workflow in the UI is a bit slow due to searching the entire home directory at one time.
Describe the solution you'd like
Recommend the following changes:
For 'init' package deployment
.zarf-cache
folderRegular Package Deployment
For 'regular' packages - the UX flow proceeds in two parts:
Search # 1.
zarf package deploy
)search part # 2
For both workflows, increase the height of the package selection table to show more packages at once
Design File
https://www.figma.com/file/MUItIzpzLBLuIyt225Bwgl/Zarf-Web-Ui?type=design&node-id=1544%3A56348&t=JeB5xVvOb7lcP6ZB-1
The text was updated successfully, but these errors were encountered: