this post was submitted on 19 Aug 2023
114 points (99.1% liked)
Technology
37739 readers
612 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I for one am recommending pulumi for any of my teams new infrastructure needs.
I used pulumi but it's much worse than terraform. I didn't used to think so before I learned terraform however.
My main reason to dislike pulumi is that you have to work around it's async behavior in python. Maybe it's better and more natural if you use typescript, but I had to constantly wrap methods in Outputs and other things to get the code to work.
I had to adapt my code to how pulumi worked all the time. With terraform, I just write it and it works.
So I'm using it with Python. For me it's able to do some stuff that terrafom never would be able to (Ive got a spot where resources are generated for each file/object on disk).
Give me an example... What file on disk are you generating a pulumi resource from?
We've got it rigged up for aws sso. Each department can make any number of permissions sets (and link to any number of groups). The config for that is all stored in git (with code owners configured so you can only mess up your own stuff).