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 refactor resource aws_emr_cluster and aws_emr_instance_group #1147

Closed
dthauvin opened this issue Jul 13, 2017 · 3 comments
Closed

EMR refactor resource aws_emr_cluster and aws_emr_instance_group #1147

dthauvin opened this issue Jul 13, 2017 · 3 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope.

Comments

@dthauvin
Copy link

Hi there,

Is there a way to refactor resources aws_emr_cluster and aws_emr_instance_group to support all functions "instance_group" (spot / autoscaling group ...) like aws api?

For example today the Core instances are driven by aws_emr_cluster resources. And not by aws_instance_group.

Terraform v0.9.11

@stack72 stack72 added the enhancement Requests to existing resources that expand the functionality or scope. label Jul 14, 2017
@dthauvin
Copy link
Author

Hello
In the last aws-sdk-go version 1.10.26 we can find some function called "PutAutoScalingPolicy" and we can set a bid price "SetBidPrice" .

If it helps.

https://github.com/aws/aws-sdk-go/blob/master/service/emr/api.go

@dthauvin
Copy link
Author

I close this issue because it's solve now with this pull request.
#1071

@ghost
Copy link

ghost commented Apr 10, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants