myADMonitor VS pq

I usually have to commit large changes in Active Directory in production environments, to accommodate merges, splits or acquisitions. I created a tool to monitor in real time the changes happening in AD so I can see if there is anything wrong or unexpected happening. For that I created this tool for personal use and I open sourced it:

https://github.com/mihemihe/myADMonitor

I wrote pq [1] (protobuf parser cli) at a company where I was told to "just use the tool another engineer wrote" which was in C++, in a really uncompileable/abandoned/unusable state

I wrote goat [2] (EBS disk attacher) at the same company on a solo project where I needed to create a "Kafka-cluster-IaC" recipe in Terraform and wanted us to be able to replace EC2 broker instances dynamically but preserve their data on the EBS volume

[1] https://github.com/sevagh/pq

[2] https://github.com/sevagh/goat

Reminds me of a tool an ex-coworker of mine wrote about 5 years ago. Check it out for inspiration maybe: https://github.com/sevagh/pq

I have a Makefile for a Rust project which binds the local repository to a Docker volume, builds it in the container using muslrust, and then does a chown to change the target directory back from root ownership to my own user.

All I had to do was 's/docker/podman/g' and remove the chown hack and it works fine: https://github.com/sevagh/pq/commit/6acf6d05a094ac2959567a9a...

It understands Dockerfiles and can pull images from Dockerhub.