I built a new tool. It is a Level 2 project harness installer (blurs into Level 3). The page is at tacoda.dev/keystone. The repo is at github.com/t...
For further actions, you may consider blocking this person and/or reporting abuse
Is there something missing? Something not working well? If you have any feedback or suggestions at all, I humbly request filing a GitHub Issue. My goal is to keep it minimal, but well-covered at
initand have the agent fill in all the discoverable stuff duringbootstrap.Update: I have opened up discussions on the GitHub project. I'd like to treat that as the gateway to work. And I already have a question! I'd appreciate your feedback here: github.com/tacoda/keystone/discuss...
Thanks!
Warning: there will likely be some churn with this tool as I learn more. 1.0 will be a solid checkpoint after the idea and design are more robust.
Update: migrations have been added as of 0.6.0. There is still file churn that is expected to happen, but now you can migrate your harness files after upgrading. I commit to always being forward-compatible. 1.0 will be a major milestone in this, but there is still more work to do before that. Thanks!
Layer 3 separation and inheritance landing today in 0.9.0!
Harness installers are the right abstraction but the install/upgrade contract needs to be the same or you get drift across teams. Looking forward to see how Keystone handles breaking changes.
Last pieces in place. There is a hierarchy in place that can be overridden with a strict option. The only thing left is some kind of authority. That will come later. Separate repos are isolated enough for now.
Part of this has been resolved.
The other part of this has been resolved: org-level policies are pulled in like packages. Still the authority issue to solve, but the minimum viable solution is in place.
Still working on the upgrade piece. For install, the harness drops into a folder in your repo - you version control it with your code, allowing others to use it.
Great work! Love to see upgrade version.