← All posts tagged cloudformation
If you wan to add element in existing list - use nested joins: ExternalBastionSecurityGroups - List<AWS::EC2::SecurityGroup::Id> SecurityGroupsList - List<AWS::EC2::SecurityGroup::Id> Outputs.BastionSecurityGroup - AWS::EC2::SecurityGroup::Id SecurityGroupsList: !Join - ',' - - !GetAtt [ securitygroups, Outputs.BastionSecurityGroup ] - !Join [ ',', !Ref ExternalBastionSecurityGroups ]
pros
— changes can be previewed before it applied (https://www.terraform.io/docs/commands/plan.html and terraform.io)
— have a modules (https://www.terraform.io/intro/getting-started/modules.html) system that allow to reuse existing configurations
— have no lock to AWS and allow to work with different resources (https://www.terraform.io/docs/providers/)
— have templating (https://www.terraform.io/docs/providers/template/)
cons
— there is no creationpolicy (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-creationpolicy.html) alternative github.com
so we have no ability to check if instance configured properly in easy way
— there is no ability to configure AWS::CloudFormation::Init (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-init.html) metadata
so we have no ability to work with host configurations that already written. (could be replaced by Chef terraform.io)
— there is no ability to work with AWS Roles yet (https://github.com/hashicorp/terraform/issues/1275)
so we need to provide AWS access and secret tokens
language support in Atom
atom.io
aws.amazon.com
aws.amazon.com
docs.aws.amazon.com
Незнаю насколько удобно будет, но визуальной части давно не хватало — что бы все зависимоти просмотреть одной кучкой.
Ну и CodeDeploy теперь в темплейты писать можно, давно пора:
aws.amazon.com