cfer icon indicating copy to clipboard operation
cfer copied to clipboard

Toolkit and Ruby DSL for automating infrastructure using AWS CloudFormation

Results 11 cfer issues
Sort by recently updated
recently updated
newest added

Fixes #50, as all cfer specs pass. Please let me know if you can reproduce any failures with this version of Docile, as I would very much like to fix...

On the `AWS::SSM::Association` object it has a property called `Parameters`, when trying to specify that in cfer like this... ``` resource :OperationsSsmPatchBaselineAssociation, "AWS::SSM::Association" do association_name "ops-patch-association" name "AWS-RunPatchBaseline" schedule_expression "cron(0/30...

Fixes #55 Generic options hash in `output` function allowed the following un-rubyish construct: ``` output :OutputName, Fn::ref(:ResourceName), Description: 'The resource that does stuff', Export: {'Name' => Fn::sub('${AWS::StackName}-OutputName')} ``` This change...

Cloudformation now allows cross-stack imports using. We should add support for `Export` in the `output` function, and `Fn::ImportValue`.

Opening this for reference until I have time to dig deeper. May be related to use of `method_missing`. I updated `docile` in bundle from 1.2.0 to 1.3.0, now all cfer...

Is there any interest in this? AWS releases the schema for cloudformation: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-resource-specification.html It would be possible to generate resources from such a schema that would allow the following: ```ruby...

Currently, it is only possible to define Metadata for a resource as an argument as such: ``` resource :instances, "AWS::AutoScaling::LaunchConfiguration", "Metadata": { } do ``` However, these sections can get...

Some properties within CloudFormation resources require lists. In Cfer at the moment, to denote this, you would need to do something like this: ``` load_balancers [{ "ContainerName": "nginx", "ContainerPort": 80,...

AWS seems to return them as a random bag. We should...not...do that.

AWS client calls fail without `Aws.use_bundled_cert!` on Windows and it appears otherwise harmless, so we should use this.