weave gitops capability for mapping error for better user experience

[enekofb]

we usually show the user the errors directly coming from our backend which are not tailored to the user expected experience.

This issue is to raise the need of having a capability with the UI for doing this mapping in the way that

• users gets error information that they could understand
• and they are suggested recover from error messages that they could act

For example an authorization error should suggest to contact the admin for further information or similar

[yiannistri]

cc @TheGostKasper @jpellizzari has there been any discussion among UI engineers about this? What do we need to do to move this forward?

[jpellizzari]

@yiannistri You want to map each possible back-end error to an enumerable error code or something like that? That would be a massive undertaking.

To me, that error messages is pretty descriptive. I don't know how we could beat it. The example given remediation steps given ("contact the admin") makes an assumption about the user's org chart...

[sympatheticmoose]

This could be a very large topic on how we want to handle and expose errors, requiring significant review from Design.

[lasomethingsomething]

@jpellizzari @enekofb Anything happen on this topic since Oct 2022? If not, should we leave open?

[enekofb]

No news and I guess that we won't be able to make the expected progress within the ticket. i have linked to the one in interlock trying to chase it through RBAC messages.

Happy if you want to close it.

[jpellizzari]

Our error messages are pretty good, and a UI experience where we suggest remedial steps is unrealistic...unless we want to train our own LLM or something :thinking:. Closing.