zxtap-to-wav VS k2tf

#bintap wget https://www.oocities.org/leetonks/Speccy/Files/bintap.zip unzip bintap.zip rename -f 'y/A-Z/a-z/' * cat bintap.c | sed 's/#include //' > bintap.c.tmp mv bintap.c.tmp bintap.c gcc bintap.c -o bintap #mktap wget https://torinak.com/~jb/zx/mktap-7.tar.gz tar -xvf mktap-7.tar.gz cd mktap-7 make #zxtap-to-wav wget https://github.com/raydac/zxtap-to-wav/archive/refs/heads/master.zip unzip master.zip cd zxtap-to-wav-master/src go build

This might be what you are looking for: https://github.com/sl1pm4t/k2tf

... and if you're an opinionated person, like me, and you value consolidated infrastructure atomicity as a whole along side locks for everything. You'd port cherry-picked helm charts as terraform modules with k2tf, and build every docker container from scratch, with forced layer invalidation to perform security updates for every image, using the docker and kubernetes providers respectively.

Pro tip: If you want to convert k8s yaml files to .tf, you can use k2tf (repo) that is able to convert the resource types of the yaml top their appropriated counterparts of the k8s provider for terraform. To install it, just:

Almost all is created as manifest/helm in K8S world, too much toil to convert (tool like https://github.com/sl1pm4t/k2tf help but exists corners cases)