tox-poetry-installer
cf2tf
tox-poetry-installer | cf2tf | |
---|---|---|
1 | 6 | |
54 | 425 | |
- | 2.4% | |
6.4 | 8.7 | |
9 months ago | 3 days ago | |
Python | Python | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tox-poetry-installer
-
How to create a Python package in 2022
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
cf2tf
-
Ubuntu Desktop 24.04 LTS: Noble Numbat
The container image for 24.04 is different from that of 22.04 and 20.04. The 24.04 container includes a "ubuntu" user with a UID of 1000, where the previous containers shipped with only a "root" user. The "ubuntu" user does not have sudo turned on by default.
This gave me issues with my vscode devcontainer setup. You can see my work around here https://github.com/DontShaveTheYak/cf2tf/pull/288/files
-
How do I convert my CloudFormation template into a Terraform file?
Not really just because there are basic limitations with certain resources mappings. You might be able to knock out reasonable chunks of busy work with something like this https://github.com/DontShaveTheYak/cf2tf
-
How to create a Python package in 2022
You can take this a step further and completely automate the release of your package. That means the tagging the publishing and the GitHub release notes.
I don't have a blog post but you can see the process on my personal project https://github.com/DontShaveTheYak/cf2tf
Check out the merged PR's and the GitHub actions.
I even do alpha releases to test pypi.
- cf2tf: A tool to automatically convert Cloudformation templates to Terraform
-
Gitflow users β What's your process for merging between develop/release/main?
I have automated this completely in several of my projects but I dont use `release` branches. Here is an example https://github.com/DontShaveTheYak/cf2tf
- Show HN: Convert Cloudformation Templates to Terraform
What are some alternatives?
pip-audit - Audits Python environments, requirements files and dependency trees for known security vulnerabilities, and can automatically fix them
cloud-radar - Create Functional and Unit tests for Cloudformation Stacks.
flitenv - π¦π Dependency manager for modern Python projects
awesome-devops - A curated list of awesome DevOps platforms, tools, practices and resources
emacs-python-exec-find - Tracks down the correct Python tooling executables from your virtualenvs so you can glue the binaries to Emacs and delete code in init.el [Moved to: https://github.com/wyuenho/emacs-pet]
roadmap - Public roadmap for the Poetry package manager
tox-pin-deps - Run tox environments with strictly pinned dependencies (and no project or code changes).
self-contained-runnable-py
release-please - generate release PRs based on the conventionalcommits.org spec
You-Python - A python library for you.com and all of its apps.
hatch-pip-compile - hatch plugin to use pip-compile (or uv) to manage project dependencies and lockfiles