Introducing BitOps v2.0! After months of heavy development, BitOps v2.0 is available for download. The new version is a major iteration of the powerful Operations Repository pattern to organize Infrastructure as Code (IaC).
The BitOps Concept
If you haven’t heard about BitOps, here’s some background. At its heart, BitOps is a tool orchestrator which is packaged with IaC tools, such as Ansible, Terraform, and others. When invoked, BitOps runs through a customizable deployment sequence and executes tools against the aforementioned Operations Repo. BitOps works great if you’d like to organize your infrastructure as code with multiple environments and manage it with simple pipelines. BitOps provides a predefined way to get started quickly without diving deep into the mechanics of the tools.
The very first BitOps version was created in
bash scripting as a quick demonstration of Operations Repository power. For BitOps v2.0, we envisioned something even more powerful.
BitOps v2.0 was fully rewritten in Python, which provides the ability to build a stronger core engine and extensibility for the future. We’re very excited about this change and looking forward to seeing how it will shape the future of BitOps with more stability, flexibility, and features.
Thanks to the new engine, you can now extend BitOps with custom plugins. Plugins are just the installation instructions for the extra tools you may need, like AWS, Ansible, Terraform or others <insert your CLI tool here>.
BitOps plugins live in a dedicated Github organization: https://github.com/bitops-plugins, where each plugin is a repository. You can even create your own plugin and build your custom BitOps Docker image with the only plugins you need. Check out the BitOps plugins documentation for more information!
Plugins provide excellent flexibility if you need a set of custom tools or elevated security. For the majority of use cases, we’ve created a default image we can recommend to our community called Omnibus.
Omnibus includes popular pre-installed tools like AWS-CLI, CloudFormation, Terraform, Kubectl, Helm, and Ansible. For your convenience, when you’re pulling
bitovi/bitops:latest docker tag, it’s referring to the latest stable
But there’s more! You can find details about the different available image bundles, their names, and respective docker tags in the section on BitOps versioning.
If you’re updating from v1.0 to v2.0, we’ve got you covered. We’ve prepared the migration guide with the list of breaking changes and instructions on how to upgrade. If you’re still running into trouble, please open an Issue or let us know in the community Slack. We’re here to support you while you upgrade!
Bi-Weekly Community Call
To streamline project progress, we’ve set up a community call every second Wednesday at 11:00 am US Central time (convert to your time zone here). On the call, we’ll discuss the ongoing BitOps work, issues, plans, ideas, and share adoption challenges and successes. We would like to invite everyone interested to join us. If you have any questions, feedback, feature requests, would like to get involved, or just to say “Hi.” Everyone is welcome!
In the first meeting, scheduled for August 31, 2022, we will discuss the future plans for the project—so don’t miss it! See BitOps Community Meetings for more info on how to join.
Call for Participation
BitOps is under rapid development. If you want to shape the future of the project:
- Try BitOps and give us feedback by opening an Issue or Bug report
- Add any topic that you think should be discussed to the meeting's agenda
- Share your adoption challenges, needs, or successes
- Give us a ⭐ on Github bitovi/bitops, if you like the project or think it's interesting
Ready to learn more? Visit our Slack #bitops channel and we’re happy to assist you any time in your DevOps automation journey!