This message was deleted.
# generals
sparse-intern-71089
07/16/2018, 11:22 PMThis message was deleted.
m
microscopic-florist-22719
07/16/2018, 11:27 PM
Hi Carlo! While we don't currently have support for provisioners ala systems like Terraform, we have started to think a bit about how we might accommodate this scenario in a first-class fashion (e.g. by exposing hooks that run user code in response to a resource's CRUD operations). In the meantime, we'd suggest deploying infrastructure that accommodates pre-provisioning; ECS with Docker or EC2 with Packer are reasonable starting points.
c
calm-summer-1743
07/16/2018, 11:41 PMah ok, thanks
s
stocky-spoon-28903
07/17/2018, 12:05 AMAs someone who saw first-hand the messes that use of Terraform provisioners produced, I’m fairly happy there is no support right now! For ages I said the best usability improvement we could have made to Terraform was deleting all the provisioners!
c
calm-summer-1743
07/17/2018, 12:19 AMha that's funny. i wonder if it's because it pulls in the config management tools that you guys are trying to replace
calm-summer-1743
07/17/2018, 12:20 AMi've been toying around with pure go based provisioning, similar to how you're doing code-based cloud provisioning
calm-summer-1743
07/17/2018, 12:20 AMit feels pretty nice so far
calm-summer-1743
07/17/2018, 12:21 AMeven if you do docker, you're still provisioning the image in bash which isn't great
s
stocky-spoon-28903
07/17/2018, 12:37 AMTo be clear, I’m only a user of Pulumi and OSS contributor 🙂
stocky-spoon-28903
07/17/2018, 12:37 AMBut yes, it was because people would do things like provision single instances, then wonder why their infrastructure failed when the instance disappeared
stocky-spoon-28903
07/17/2018, 12:38 AMVersus running things in autoscaling groups with ready-to-rock images
2 Views