Re:The architecture of declarative configuration management
by cosaquee on Friday November 15, 2019 @02:10AM
(#21542916)
Cloud formation is after lacking support for resources that are new or less popular. Terraform is much better in this, supports most of the resources from the start as far as I know
Re:The architecture of declarative configuration management
by xmly on Friday November 15, 2019 @08:27PM
(#21550339)
In cloudformation, you could customize your resource types with aws lambda. It is like creating the providers in terraform.
Plus, cloudformation is free and managed service. You do not need to maintain and it is wrong, you could yell at AWS. Unless you bought terraform enterprise, it is still a pain to maintain another possible failure point in your system.
Re:The architecture of declarative configuration management
by paulddraper on Friday November 15, 2019 @02:16AM
(#21542940)
Considering the staggering breadth of AWS, it is amazing how fast and completely Terraform supports AWS.
Only a couple times have I actually encountered unsupport features (1. global WAF 2. non-canned S3 bucket policy)
And for Prod env, what are discussing sounds like update behavior for me. In cloudformation, you could choose the different update policies.
Comparing with each cloud's provisioning engine, cloudformation/gcloud deployment manager/azure resource manager, terraform is lacking a lot of features. So unless you are dealing with a private cloud, using cloud default provisioning service is a no-brainer.