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

Add Support Optional Components Configuration in Dataproc Beta Provider #3075

Closed
d20tech opened this issue Feb 18, 2019 · 2 comments
Closed
Assignees

Comments

@d20tech
Copy link

d20tech commented Feb 18, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

The beta release of Google Cloud Dataproc allows users to specify optional components that will be installed on a cluster at startup time. This property is specified on the SoftwareConfig element of the clusters.create command as described here: https://cloud.google.com/dataproc/docs/reference/rest/v1beta2/ClusterConfig#Component

Terraform does not expose this property in its software_config element, thus clusters can not be created using this feature.

New or Affected Resource(s)

  • google_dataproc_cluster

Potential Terraform Configuration

resource "google_dataproc_cluster" "mycluster" {
    # ... 
    software_config {
        optional_components = [ "ANACONDA", "JUPYTER" ]
    }
}

References

@ghost ghost added the enhancement label Feb 18, 2019
@megan07 megan07 self-assigned this Jul 22, 2019
@megan07
Copy link
Contributor

megan07 commented Jul 29, 2019

Thanks @d20tech for opening this issue. It's been closed with #4073 and will be released shortly.

@ghost
Copy link

ghost commented Aug 29, 2019

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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Aug 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants