November 15, 2020
by
Dominik Dorosz
Having strong ownership of your microservices and other running systems is an important pre-requisite to building a DevOps culture. But focusing solely on ownership of services running in production can leave some gaps. There’s a lot of code living outside of any service’s codebase: libraries, internal tools, templates, terraform code, and a lot more. All of these repositories need ownership too.
Having strong ownership of all your repos comes with a lot of benefits:
- Authority: There’s a team in charge of setting the standards for contributing to and making changes to the code.
- Accountability: There is a team responsible for fixing bugs or vulnerabilities when they’re found.
- Security/Compliance: Some compliance frameworks have an implicit requirement of all tier-1 software having strong ownership, so that critical security vulnerabilities don’t go unseen.
We’re proud to announce OpsLevel’s new Repository Ownership feature.
With Repository Ownership, you can:
- Explicitly define the ownership of each of your repos, using config-as-code (or through our GraphQL API).
- See how your repos map to your services, both for 1:1 mappings or mono-repo environments.
- Understand what tier of services your repository is already supporting - or set/override your repo’s tier explicitly.
- Track extra repository metadata through tagging.
To learn more about our new repository ownership feature, visit our docs page.