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

Feature Request: Resource for managing AWS Glue Developer Endpoints #3876

Closed
bflad opened this issue Mar 22, 2018 · 6 comments
Closed

Feature Request: Resource for managing AWS Glue Developer Endpoints #3876

bflad opened this issue Mar 22, 2018 · 6 comments
Labels
new-resource Introduces a new resource. service/glue Issues and PRs that pertain to the glue service.

Comments

@bflad
Copy link
Member

bflad commented Mar 22, 2018

Split feature request from #1416. For issues not immediately being worked on, please use 👍 upvotes on this original issue comment to help guage community interest.

Terraform Version

terraform 0.10+
terraform-provider-aws (new feature)

Affected Resource(s)

  • aws_glue_dev_endpoint

Terraform Configuration Files

# New Resource - not implemented
resource "aws_glue_dev_endpoint" "example" {
  # ...
}

Expected Behavior

Create, read, update, and delete support for AWS Glue developer endpoints.

Actual Behavior

Resource not implemented.

References

@bflad bflad added new-resource Introduces a new resource. service/glue Issues and PRs that pertain to the glue service. labels Mar 22, 2018
@rangerscience
Copy link

rangerscience commented Aug 9, 2018

Ah, this is what I'm looking for!

I'm interested in trying to contribute to Terraform (love this product, you guys, it's amazing), this seems like a reasonable place to start... but I'm not that familiar with Go or the Terraform code (just it's usage). Any pointers? Both the raw "getting setup to dev TF" (although there's stuff in the contribution guidelines for that) and the "how to effectively stare at our code" would be appreciated.

My use case it making it easy to boot up (and tear down) a Zeppelin notebook; they're amazing, but expensive to keep running.

I have a working CloudFormation template for the dev endpoint (if that would be helpful); the Zeppelin CF template then relies on some values that come from the dev endpoint that are accessible via the AWS CLI; presumably, this means if there's a Terraform resource for the dev endpoint, they'd be usable in a CF template managed by TF, even if a Zeppelin notebook resource is beyond the TF scope (which... is likely, looking at the CF template).

@xmj
Copy link

xmj commented Oct 18, 2018

Out of curiosity, has this feature request already been taken into the roadmap for the TF AWS provider?

@jckuester
Copy link
Contributor

I added a PR that adds the resource aws_glue_dev_endpoint: #7895

@xmj
Copy link

xmj commented Mar 13, 2019

Thanks @jckuester!

@DrFaust92
Copy link
Collaborator

Closed via #7895

@ghost
Copy link

ghost commented Dec 14, 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!

@hashicorp hashicorp locked as resolved and limited conversation to collaborators Dec 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-resource Introduces a new resource. service/glue Issues and PRs that pertain to the glue service.
Projects
None yet
Development

No branches or pull requests

5 participants