[deployer] Save a chosen app selection as a named, reusable setup #287
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/home#287
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Once an operator has chosen a set of apps for a user, they should be able to name and save that selection as a reusable setup, for example a teaching environment or a coding environment, and apply the same setup to later users without choosing the apps again. Saved setups are what make standing up a consistent group repeatable, and they depend on the app catalog item. Tracked under #285.
Signed-by: mik-tf mik-tf@noreply.invalid
mik-tf referenced this issue2026-06-15 22:15:42 +00:00
Saved setups are implemented and live on the testing organization admin instance. An operator can now build an app selection on the Add and set up form, name it, and save it as a reusable setup (the chosen apps plus a release channel); a setup picker reapplies it to later members, and Save as setup or Delete manage them. Saving the same name updates that setup rather than creating a duplicate, and the saved apps are checked against the catalog so only real, installable apps are stored. Verified end to end on the live admin instance: save, list, re-save (update in place), and delete, with the test setup removed afterward so the live data stays clean.
Signed-by: mik-tf mik-tf@noreply.invalid
mik-tf referenced this issue2026-06-16 05:58:55 +00:00