Nullstone serves as a single source of truth for infrastructure.
This data could be expanded to include operational and organizational metadata so that development teams can use Nullstone for discovery and as a single pane of glass.
How will it work?
The overview page for each block (e.g. app, datastore, subdomain) is expanded to include custom metadata configurable by the organization. Specifically, the block owners are allowed to edit the metadata.
Here is sample metadata that is useful to many teams.
Owner
On-Call
Github app README.md
Tags
App to app dependencies
Open questions
Do all teams have standard fields that always exist (service owner, who is on call, etc)?
Who is allowed to edit the metadata?
Smaller teams may not want metadata; can teams disable this functionality (per stack, per org)?
How do we provide hooks to enrich the data? (e.g. on-call from OpsGenie)
Overview
Nullstone serves as a single source of truth for infrastructure. This data could be expanded to include operational and organizational metadata so that development teams can use Nullstone for discovery and as a single pane of glass.
How will it work?
The overview page for each block (e.g. app, datastore, subdomain) is expanded to include custom metadata configurable by the organization. Specifically, the block owners are allowed to edit the metadata.
Here is sample metadata that is useful to many teams.
Open questions