Dumont, the tower guardian, is a service for managing versions and the state they are in.
Kevin creates a new version 1.6.9
of clu
is created to fix the phone bill problems. Before Kevin
sends clu
out on his mission, he'll want to know what version was built and attach a version
to git hash. Since only one clu
can be on mission at a time, Kevin would update 1.6.9
's labels
to denote that it was deployed and when.
In the mean time, Kevin goes and adds more improvements to clu
and build version 1.7.1
. When
the day ends, Kevin goes home thinking that 1.7.1
is on a mission. When Kevin arrives back at work,
he notices that clu
gave an error that he thought he fixed. Instead of digging into the code, Kevin
asked dumont
what version was deployed, realized the mistake and send 1.7.1
out to fix the phone
bill.
We have them! See them at docs/api.md!
- Normal github style organization. (org/repo/version)
- Policy enforcement for required labels on repos and versions.
- Multiple policies can be applied based on org/repo names.
- Postgresql backend.
- Tested.
- Authentication. Authentication is hard, and best done by another application like nginx. See this blog post for how to do mutual auth (x509) with nginx.
- Authorization. This is a feature that could be added in the future, but is currently missing.
- Dependency management. ANGTFT, you would use
dumont
inside other applications to determine if versions are being used that shouldn't be. - Search. It's hard and coming soon hopefully!