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
Currently, users can add new destination and add configuration options for them.
If there is an issue with the configuration, for example if the endpoint is invalid, odigos auto-scaler component will log the error and will not show any indication in the UI.
This issue is to add indication for the destination. So if everything goes well, the destination should indicate it, and if there are errors, I want to have the error message so the user can fix it.
To do that, we will need:
Add Status to the destination CRD here which should include Conditions similar to the ones in actions.
For all destinations, return an error from the ModifyConfig function, and write the error to the destination CRD or indicate success if there is no error. This should be applied here.
After this step, the user can see any status and error in the CRD. The next step after this is done would be to report this data in the frontent code so it is accessible to odigos UI.
The text was updated successfully, but these errors were encountered:
Currently, users can add new destination and add configuration options for them.
If there is an issue with the configuration, for example if the endpoint is invalid, odigos auto-scaler component will log the error and will not show any indication in the UI.
This issue is to add indication for the destination. So if everything goes well, the destination should indicate it, and if there are errors, I want to have the error message so the user can fix it.
To do that, we will need:
Status
to the destination CRD here which should includeConditions
similar to the ones in actions.ModifyConfig
function, and write the error to the destination CRD or indicate success if there is no error. This should be applied here.After this step, the user can see any status and error in the CRD. The next step after this is done would be to report this data in the
frontent
code so it is accessible to odigos UI.The text was updated successfully, but these errors were encountered: