shalomb/tofu

A terraform-on-openstack dynamic inventory for ansible.

Shalom 👋

• 🔭 I’m currently working on my fatherhood skills, rum, terraform providers for $work
• 👨 At $dayjob I do {cloud,devops,platform} Engineering on the Takeda Enterprise Cloud
• ⚡ I'm a big proponent of DevOps - both the practices and principles. You can't remain effective in any domain/vertical without DevOps nowadays - prove me wrong!
• 🌱 I dabble in Distributed Systems, Linux, Cloud Native Tech, Golang, Python, Rust
• 👯 I’d like to work on something nebulous yet lofty (☁️ "cloud-native". get it?) with a nautical (☸) twist .. heh.
• 🤔 I’m looking for help tackling this Strava segment 🚴
• 📫 How to reach me: shalomb.id/#contact

What I do

---

tofu's Issues

Usage of modules not supported

tofu will only report resources in the root of the terraform state tree.

The problem is in L111: this assumes there is no terraform module being used except for the main, root definition.

Instead of hardcoded value of 0, self.data.modules should iterated because the length can be n.

An example from a more complex terraform infra using modules:

>>> len(data['modules'])
8
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][0]['resources'].keys() )
[]
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][1]['resources'].keys() )
[]
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][2]['resources'].keys() )
[]
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][3]['resources'].keys() )
[]
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][4]['resources'].keys() )
[]
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][5]['resources'].keys() )
[u'openstack_compute_instance_v2.vm_2n.0', u'openstack_compute_instance_v2.vm_2n.1', u'openstack_compute_instance_v2.vm_2n.2']
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][6]['resources'].keys() )
[u'openstack_compute_instance_v2.vm_2n.0', u'openstack_compute_instance_v2.vm_2n.1', u'openstack_compute_instance_v2.vm_2n.2']
>>> filter( lambda x : re.search('openstack_compute_instance_v2', x), data['modules'][7]['resources'].keys() )
[u'openstack_compute_instance_v2.instance']

This is because in this tf infra there is no vm being built in the root, but only using modules.

Project `tofu` on test.pypi.org

Hi! I'm one of the moderators of PyPI. In pypi/support#147 a different user is asking to be able to use the tofu name or test.pypi.org like they can on pypi.org. It looks like you may have earlier published a package under that name. Could you please respond to that issue?

Thank you!