Hide Advanced Parameters on Nested Services #204

Closed
opened 2025-09-26 12:39:51 +00:00 by tobru · 2 comments
Owner

Stories

As a user, I want to not get overloaded by too many parameters in the service form

Implementation Notes

Some services, like Nextcloud or Keycloak nest other services like PostgreSQL. A nested service like PostgreSQL has a multitude of parameters, which are in themselves quite complex.

In this case, this is spec.parameters.service.postgreSQLParameters. Hide these parameters by a toggle "Advanced" button which either shows or hides these parameters.

We need to make the field(s) configurable in the service definition, because this can differ depending on the service definition. Make this an array and put all fields configured this way behind an advanced button.

BTW: postgreSQLParameters leads into Postgre s q l parameters in the frontend which isn't so nice.

## Stories _As a user, I want to not get overloaded by too many parameters in the service form_ ## Implementation Notes Some services, like Nextcloud or Keycloak nest other services like PostgreSQL. A nested service like PostgreSQL has a multitude of parameters, which are in themselves quite complex. In this case, this is `spec.parameters.service.postgreSQLParameters`. Hide these parameters by a toggle "Advanced" button which either shows or hides these parameters. We need to make the field(s) configurable in the service definition, because this can differ depending on the service definition. Make this an array and put all fields configured this way behind an advanced button. BTW: `postgreSQLParameters` leads into `Postgre s q l parameters` in the frontend which isn't so nice.
tobru added the
enhancement
label 2025-09-26 12:39:51 +00:00
tobru added this to the Development Planning project 2025-09-26 12:39:51 +00:00
rixx referenced this issue from a commit 2025-10-17 03:44:54 +00:00
Author
Owner

While it works with fields like spec.parameters.backup.schedule I couldn't see it working with the fields spec.parameters.service.fqdn or spec.parameters.service.postgreSQLParameters

While it works with fields like `spec.parameters.backup.schedule` I couldn't see it working with the fields `spec.parameters.service.fqdn` or `spec.parameters.service.postgreSQLParameters`
Author
Owner

It now works as expected and looking great 💯

It now works as expected and looking great 💯
tobru closed this issue 2025-10-22 13:20:20 +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#204
No description provided.