tox-poetry-installer VS awesome-devops

This is almost exactly how I set up python projects; it’s reassuring to see it set out in one place.

I started using tox-poetry-installer[1] to make tox pick up pinned versions from the lock file and reuse the private package index credentials from poetry.

[1] https://github.com/enpaul/tox-poetry-installer

I would start with awesome devops and drill down there to which tools and projects are open source and in go. I know that Terraform is in go, Docker itself is in go, some projects that I use like Telegraf are in go too, but a comprehensive list of all tools that can be used by devops, that are open source and in go may be huge. Is better to get a very partial list and pick from there the ones you find more interesting, both in mission and in code.

github.com/wmariuss/awesome-devops

Not necessarily, it just depends on how invested you are in the CI/CD pipeline for any given project, your preferences regarding self-hosting vs. cloud, and the amount of time you have to dedicate to the subject.

Strictly speaking, any tool or set of tools that allow you to trigger building & deploying/publishing artifacts in response to source control commits can be used to build a CI/CD pipeline. One could write bash scripts linked to a cron job that pulls a remote repository every n minutes and then performs some scripted actions to integrate changes between branches before building & publishing the artifact to a local SFTP server.

If you prefer a more mature solution with better documentation however, there is a (non-exhaustive) list of CI/CD tools on this awesome-devops list:

https://github.com/wmariuss/awesome-devops#continuous-integr...