Feature request: "worker type" and "number of workers" arguments on aws_glue_job resource

[vasili-zolotov]

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

Description

AWS Glue team has introduced new worker types to support memory intensive and ML workloads on Glue. This brings the requirement to support "worker type" and "number of workers" agrumnets on the aws_glue_job resource.

See the announcement: https://aws.amazon.com/about-aws/whats-new/2019/04/aws-glue-now-supports-additional-configuration-options-for-memory-intensive-jobs/

New or Affected Resource(s)

• aws_glue_job

Potential Terraform Configuration

resource "aws_glue_job" "job_id" {
  name                        = "job-name"
  worker_type             = "G.1X"
  number_of_workers = 10
  # other arguments
}

References

• N/A

[bflad]

Support for the number_of_workers and worker_type arguments to the aws_glue_job resource has been merged and will release in version 2.39.0 of the Terraform AWS Provider, likely tomorrow. Thanks to @Zambonilli for the implementation. 👍

[ghost]

This has been released in version 2.39.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

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!