Consider using a non-null value for unknown cluster authorization type

The following discussion from gitlab-ce!24119 should be addressed:

  • @DylanGriffith started a discussion: (+2 comments)

Andreas gave a good suggestion that it's better to use explicit values. Is there any reason we chose null? If we moved away from null it would actually help with simplifying the model since we'd use DB level defaulting.

Assignee Loading
Time tracking Loading