Comment by dotwaffle
6 hours ago
Needing to list an "executive sponsor" (an individual, not a role or a team) for each and every item in a service catalogue seems like mindless bureaucracy.
Meanwhile, having "custom properties" attached to each repo feels very much like administering JIRA, and schema-less YAML blobs that pervade the GitOps world.
Is it just me, or isn't the glaringly obvious solution to this an actual database and API, rather than just tacking on random bits of metadata that have no real-time validation etc?
As to the "executive sponsor" -clearly this is going to result in more "god" repos which keep accumulating responsibilities because nobody can be arsed to go through the official approval channels.
Source: my workflow once they required various TPS forms to be completed before you were allowed to create a new repository.
This is Microsoft we're talking about, they'd never do the glaringly obvious solution when mindless bureaucracy is an option.