Service Configuration Form Mandatory Field Handling #156

Open
opened 2025-07-17 12:37:19 +00:00 by tobru · 0 comments
Owner

Stories

As a user, I want to have a meaningful service configuration form in regards to mandatory fields.

Implementation Notes

  • Show all mandatory fields in a separate section so that when creating a service instance it's clear which fields need to be filled out for successfull creation
  • The mandatory field detection doesn't catch all of them. For example, in VSHNNextcloud, some mandatory fields are not properly marked as mandatory, even when defined in the API spec: spec.parameters.service.fqdn or spec.parameters.service.collabora.*.
## Stories _As a user, I want to have a meaningful service configuration form in regards to mandatory fields._ ## Implementation Notes * Show all mandatory fields in a separate section so that when creating a service instance it's clear which fields need to be filled out for successfull creation * The mandatory field detection doesn't catch all of them. For example, in VSHNNextcloud, some mandatory fields are not properly marked as mandatory, even when defined in the API spec: `spec.parameters.service.fqdn` or `spec.parameters.service.collabora.*`.
tobru added the
enhancement
label 2025-07-17 12:37:19 +00:00
tobru added this to the Development Planning project 2025-07-17 12:37:19 +00:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: servala/servala-portal#156
No description provided.