We’ve just hit this point in our project (packit) that we want to split it to two repositories: CLI tool and a web service. I was thinking of keeping the git history for files I want to move to the other repository. There is a ton tutorials and guides how to do such a thing. This is what worked for me: Clone the original repository. Have a list of files I want to remove:
I wanted to update my gentoo box once again. I did last update probably ~6 months ago. This usually means for me that I get a ton of conflicts:
Exciting times! I just released ansible-bender-0.5.0.
This update contains a ton of new stuff. There is the one feature I am very proud of — configuring the build process by using Ansible variables. Apart from that, I did a lot of bug fixes and usability improvements.
PoC Definition: Can ansible-bender run inside an OpenShift origin pod?
Answer: Yes!
For the past couple of months, I’ve been working on a project we call “Ansible OCI image builder”. I named the tool itself ansible-bender (and yes, it’s shiny).
I’m pleased to announce that
ansible-bender is now
available in version 0.2.0.
Sam Doran just merged my pull request which introduces a new connection plugin for podman. If you are not sure what an Ansible connection plugin is, hold tight and I’ll show you.
The connection plugin is the component which enables Ansible to execute commands in a target environment: you are probably mostly familiar with these two:
Since Ansible abstracts this mechanic very well, you can easily write connection plugins for such a thing as container managers. Ansible has one for docker and some time ago I wrote one for buildah. I concluded it’s time to write it for podman as well, finally (so I can utilize it in ansible-bender).