Details
-
Story
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
5
-
March 26, April 9, April 23
Description
Argument validation is somewhat haphazard right now (though not catastrophically bad because we have a lot of constraints in the DB)
It needs to become more systematic, driven off some metadata description of commands, which clients incidentally could also use to understand commands.
There are also cases where raw postgres errors are sent back to clients (e.g. when trying to create a policy with a name that is in use already)
Attachments
Issue Links
- is blocked by
-
RAZOR-78 Invalid JSON does not fail as it should.
-
- Closed
-
-
RAZOR-132 Razor Fails to Create Repository if the Repository Name Contains Unicode Characters
-
- Closed
-
-
RAZOR-68 Cannot get help for a specific subcommand
-
- Closed
-
-
RAZOR-144 Confusing error message creating a rule
-
- Closed
-
- relates to
-
RAZOR-178 Better argument validation and error messages for remaining commands
-
- Closed
-
-
RAZOR-191 Validation should be more precise about what has failed, for nested structures
-
- Closed
-