Show reason for unauthorized access on AI Explorer pages (e.g., speech_to_speech_generator, translation_generator, image_classification_generator, audio_to_audio_generator)

So changing the actual message on the page would need some refactoring, since you would have to make the listings page aware that the route in the routing file is allowing the route, but the form controller should throw the exception. This could also add security issues, so it should be done with care.

For now I added so the error message gets logged:
→ .

If you feel like this is a good enough soluion, please set to RTBC, otherwise set back to needs work.

I suggest not displaying the link to the explorer in the explorers' listing at all if the currently configured provider(s) do not support an operation. If that is already working, then we do not need to do anything in this, I guess.

Yes, its already not showing in the listing, since its not accessible - in this case it was just to improve the information to any developer that has figured out the endpoint by themselves.

I am moving to RTBC

Then we consider this fixed - 1.2.x is the new target, 1.1.x will just take bug issues from now on.

Automatically closed - issue fixed for 2 weeks with no activity.

marcus_johansson → closed merge request !614