Service Plans #308
No reviewers
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: servala/servala-portal#308
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "264-service-plans"
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?
Implemented: Service plan model, selection on instance create, update in instance update form. Ref #264
The data model, as well as the backend with the Kubernetes API: LGTM. It works as expected and I think the data model should work.
The front-end part needs some work, though. A service might have many plans to choose from; as it is currently designed, this would take too much space. I propose to offer the plans in a dropdown. The design of the individual plan card looks nice. Maybe we can keep the same with a custom dropdown? Also, the visual representation of the storage should look and feel more similar to the plans; right now it's a bit too different.
WIP: Service Plansto Service Plans