-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FromPort, ToPort and Egress are optional #463
Commits on Apr 18, 2016
-
FromPort, ToPort and Egress are optional
Those 3 properties are flagged as optional in AWS's docs.
Configuration menu - View commit details
-
Copy full SHA for b806b47 - Browse repository at this point
Copy the full SHA b806b47View commit details -
Egress is actually required, Ingress is conditional
Made a mistake in my previous commit - this one actually reflects the docs.
Configuration menu - View commit details
-
Copy full SHA for c664b69 - Browse repository at this point
Copy the full SHA c664b69View commit details -
Subclassed Template into an object able to analyze and create Troposphere objects based on an existing CloudFormation Template. Conditions are missing - working on it.,
Configuration menu - View commit details
-
Copy full SHA for 2a67cd9 - Browse repository at this point
Copy the full SHA 2a67cd9View commit details -
Configuration menu - View commit details
-
Copy full SHA for e3cb6ed - Browse repository at this point
Copy the full SHA e3cb6edView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4ad57ba - Browse repository at this point
Copy the full SHA 4ad57baView commit details
Commits on Apr 19, 2016
-
EMR configuration_validator removed
This removal helps inspection of the Configuration class to enable automating troposphere object creation.
Configuration menu - View commit details
-
Copy full SHA for 7a98705 - Browse repository at this point
Copy the full SHA 7a98705View commit details -
Added UpdatePolicy, CreationPolicy, DeletionPolicy, Metadata and DependsOn discovery.
Configuration menu - View commit details
-
Copy full SHA for e4fd394 - Browse repository at this point
Copy the full SHA e4fd394View commit details -
Special AWSHelperFn typically take lowercased parameters, but templates use uppercase. for this reason we cannot map to most of them, so we fallback with a generic one. This might not work for all types if they do extra processing in their init routine but makes tests pass :)
Configuration menu - View commit details
-
Copy full SHA for 4d0f0f4 - Browse repository at this point
Copy the full SHA 4d0f0f4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1b8c79d - Browse repository at this point
Copy the full SHA 1b8c79dView commit details -
Fix S3 Bucket using name instead of title
S3 Bucket used a 'name' argument and put that into the 'title' of the AWSBaseObject. This modification is backward compatible and allows 'name' to be substituted by 'title' in the kwargs.
Configuration menu - View commit details
-
Copy full SHA for 10ee2f6 - Browse repository at this point
Copy the full SHA 10ee2f6View commit details -
Configuration menu - View commit details
-
Copy full SHA for ae20dce - Browse repository at this point
Copy the full SHA ae20dceView commit details -
Remove unnecessary AWSHelperFn from props
AWSHelperFn are ignored in AWSObjectBase, it's not necessary to flag them in props anymore.
Configuration menu - View commit details
-
Copy full SHA for 89caac9 - Browse repository at this point
Copy the full SHA 89caac9View commit details -
Configuration menu - View commit details
-
Copy full SHA for e64c26a - Browse repository at this point
Copy the full SHA e64c26aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6c99e26 - Browse repository at this point
Copy the full SHA 6c99e26View commit details