Skip to content
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

Emr configurations values: also allow AWS helper functions #516

Merged
merged 4 commits into from
Jul 2, 2016

Conversation

cbamelis
Copy link
Contributor

The current master branch contains a too strict EMR configurations validator method: this validator forces configuration values to be strings. CloudFormation also allows helper functions (which allow you to use for instance a parameter value as configuration value instead of a direct string value).

This branch contains an updated validator method and updated EMR cluster example using an indirect configuration value.

I also updated the EMR example with a parameter dependent choice between spot instances or on-demand instances (using a 'condition').

The EMR example is successfully created in my AWS region eu-west-1.

@markpeek markpeek merged commit d4d0cee into cloudtools:master Jul 2, 2016
@markpeek
Copy link
Member

markpeek commented Jul 2, 2016

Thanks!

amosshapira pushed a commit to amosshapira/troposphere that referenced this pull request Oct 24, 2016
…s#516)

* Added parameter to dynamically choose between spot and on-demand instances

* Fixed EMR configuration properties validator: both strings and helper functions are allowed by cloudformation

* Prevent lines with more than 79 characters to make Travis CI happy

* Fixed EMR configuration properties validator: both strings and helper functions are allowed by cloudformation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants