MonsantoCo / cloudformation-template-generator

39%

master: 53%

LAST BUILD ON BRANCH rds-encrypt

branch: rds-encrypt

CHANGE BRANCH

x

Reset

• rds-encrypt
• AWSConfig
• IAMPolocyVersion
• NatGateway
• RDSMaker
• adamfokken-route-vpngateway
• autoscaling-ebs
• db_and_volume_types
• depends-on-strings
• determinism
• elasticsearch
• expand-ElastiCache
• fix-condition-functions
• ip-address-type
• issue104
• master
• nat-gateway
• natbuilder
• nestable-not
• remote-route53
• remove-dupes
• route53-race-fix
• template-exports
• template_implicits
• v2.0.2
• v3.0.0
• v3.0.1
• v3.0.2
• v3.0.3
• v3.0.4
• v3.0.6
• v3.1.0
• v3.1.1
• v3.1.2
• v3.2.0
• v3.3.0
• v3.3.1
• v3.3.2
• v3.3.3
• v3.3.4
• v3.3.5
• v3.4.0

Build # 20

Build Type

push

travis-ci

Committed by ddgenome

Commit Message

Reduce ability to create invalid RDS template

Implement a complex mechanism for reducing the chance of creating JSON
for an RDS DBInstance that is invalid.  My hope is that the complexity
equals and is not greater than the complexity inherent in the
restrictions around RDS creation.  There is still one run-time check
around storage encryption since specifying it is only valid on new
instances created within VPCs.

There are restrictions on the values of AllocatedStorage when using
Iops but often these values are given as parameter and therefore must
accept Token[Int].  I currently used Either to take Int or Token[Int]
but at some point it would be good to allow one to reach through the
Token to see if the Int is there too test.

Tests were added to cover all of the above.

A couple other minor changes:
-   Clean up build.sbt
-   Implement and use EnumFormat for all enumerations JSON serialization

Run Details

357 of 918 relevant lines covered (38.89%)

0.39 hits per line