Improve detection of mandatory fields #201
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: servala/servala-portal#201
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?
Stories
As a user, I want to only enter mandatory fields during service creation
Implementation Notes
For example, the Nextcloud service has a parameter
spec.parameters.service.collabora.fqdnwhich is marked as mandatory in the OpenAPI spec, but is only really mandatory whenspec.parameters.service.collabora.enabled=true, otherwise it's not mandatory to fill in this field. ext docs.Find a way to cope with this situation, so that this is working as intended in the portal frontend.
For now we change the field in the backend: https://vshnticket.atlassian.net/browse/APPCAT-1188 This way we "buy us some time" in the portal.