[GitHub] [trafficcontrol] moltzaum opened a new issue #3574: 'privLevel' cannot be blank message when privLevel is 0

[GitBox <gi...@apache.org>]

moltzaum opened a new issue #3574: 'privLevel' cannot be blank message when privLevel is 0
URL: https://github.com/apache/trafficcontrol/issues/3574
 
 
   When I post a role with a privLevel of 0, it tells me that the privLevel cannot be blank.
   
   ```
   {
       "name": "foo",
       "description": "all access to foo",
       "privLevel": 0,
       "capabilities": []
   }
   ```
   
   `curl -XPOST --cookie $mc -Lvsk 'https://localhost:6443/api/1.4/roles' -d @role.json | jq`
   ```
   {
     "alerts": [
       {
         "text": "'privLevel' cannot be blank",
         "level": "error"
       }
     ]
   }
   ```
   
   This is a minor bug, which can probably be ignored. I doubt anybody would _want_ to create a role with a privLevel of 0, but we have the disallowed role, which does just that.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services