Closed ihiverlet closed 2 weeks ago
At the moment :
values.schema.json
file https://github.com/InseeFrLab/onyxia-api/blob/5bd597127bbeeb22d155494d9632dfcaf1c28d1d/onyxia-api/src/main/java/fr/insee/onyxia/api/controller/pub/CatalogController.java#L147With this behavior, onyxia release will have his own metadata and we will be able to let user modify configuration ( friendly name , sharing ) with touching the helm chart
Hi !
As of today, when launching a service, Onyxia metadatas (such as the friendly name of a service) are stored in values.yaml files.
A cleaner way to handle such metadata would be to create a secret with all relevant information. This secret could be created ad hoc thanks to the API and be attached to the right helm release via the owner reference.
Not only this could allow us to have a better handling of metadata but the secret would also be deleted when doing an
helm uninstall
.An example of such a secret :