Pipeline quota errors should say what the actual limit is
Problem
When a pipeline is immediately dropped, while being created, due to exceeding some of the pipeline limits we display the following error:
This error message doesn't really say what the actual limit is. The admin would be aware of the limit but any other user wouldn't know that.
To let the pipeline author adjust their pipeline accordingly we should tell the user what the actual limit is.
Solution
-
@fabiopitino started a discussion: (+2 comments) Should we tell the user what the actual limit is? I know we return the exact same message on other limits but a non admin may not know what the limit is unless they have to work it out from the exceeded number.
Should we also fix it in other quota classes?
Edited by Fabio Pitino