beelit94
you still alive my bro? I want to maintain this
@kirankotari @sammck @aubustou @BNMetrics @jaustinpage i see you guys have contributed to this project so if you guys have access to this repo and can maintain this !! or we can clone and comeup with new one.
Thanks, Janibasha
It looks like I still have merge in here, I haven't used TF in like 5 years, but if I can give someone else merge I will, poking around at settings for the repo.
It looks like I still have merge in here, I haven't used TF in like 5 years, but if I can give someone else merge I will, poking around at settings for the repo.
It would be great if this library went back into maintenance. It seems to work at a basic level with the latest release of the library and terraform; however, some workaround is required. The one issue I encountered I had to work around, but it appears to be already fixed in the latest develop branch.
If @LeOndaz wants to maintain it, it'd be nice if they did.
It looks like I still have merge in here, I haven't used TF in like 5 years, but if I can give someone else merge I will, poking around at settings for the repo.
It would be great if this library went back into maintenance. It seems to work at a basic level with the latest release of the library and terraform; however, some workaround is required. The one issue I encountered I had to work around, but it appears to be already fixed in the latest develop branch.
If @LeOndaz wants to maintain it, it'd be nice if they did.
I'm open to it, but I'm not sure where/whom to reach out
I'm open to it, but I'm not sure where/whom to reach out
It appears that @Spikeophant has access to set you up with merge access.
Of course, worst case, this could be forked. But I guess you'd lose all of the outstanding issues and PRs currently associated with this repo.
I don't have merge and haven't used in years, but agree that someone with a vested interest should maintain. Provided they aren't a nation state spy ;).
@merpius @sammck @janibashamd @Spikeophant it's worth mentioning that it's been almost a year since this issue was opened, most likely I can reclaim the name python-terraform from Pypi, I also think it's not worth a fork, I think a new async implementation would be nicer, most people are using/moving to async these days, sqlalchemy did, django is doing that, so I think it's worth a shot
Please, think out loud and share that with me
True it has been a long time, however Spike only replied 2 days ago. :D So I think there's hope.
As for if it cannot be regained, a new implementation utilizing async seems reasonable, but probably a decent amount of work to get initially set up. If you're up for it, go for it.
wops, I didn't notice the collaborator badge, this makes things much easier, I will wait till we get all the opinions
@merpius I would like to add something, in some apps, I'm using Pulumi, instead of Terraform, they have python bindings and some people are using SST (sst.dev, I think it's an interface around Pulumi), if you still have the option to decide, most likely you'll ditch terraform, if not, understandable
I don't see that I have the ability to add additional collaborators with merge permissions.
+1 to TofuPy mentioned above, just tested and looks solid. cool work @tedivm!
