You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2023. It is now read-only.
When deploying new catalog chart version for an onyxia catalog, we dont need to redeploy onyxia api since the api could fetch the catalog based on configuration settings.
Anyway there is no real visual indication about when the catalog is updated, when there is multiple api pod the problem could be harder as one api could have updated catalog and another not yet.
Workaround
Display in each card the version of the chart in the catalogue in small caracter ( the api already give it in /catalog endpoint)
The text was updated successfully, but these errors were encountered:
In case of multiple instances of api, we could extend this feature to include the chart version in the request (payload or header) the instance of api on which the request will be send could :
if version of the chart sent is the same that his current version chart
then
the instance could handle the request
else
on your choice return an error or force the refresh of catalog.
Add information about catalog and chart version
Issue
When deploying new catalog chart version for an onyxia catalog, we dont need to redeploy onyxia api since the api could fetch the catalog based on configuration settings.
Anyway there is no real visual indication about when the catalog is updated, when there is multiple api pod the problem could be harder as one api could have updated catalog and another not yet.
Workaround
Display in each card the version of the chart in the catalogue in small caracter ( the api already give it in /catalog endpoint)
The text was updated successfully, but these errors were encountered: