-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[Enhancement]: aws_glue_job new worker types #33862
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Agreed. This was added to Glue May 9th 2023. So its been some time since the feature was available. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.46.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. Thank you! |
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. |
Description
Terraform v1.5.7
Seems that terraform supports only 3 worker types:
Error: expected worker_type to be one of [Standard G.1X G.2X G.025X], got G.4X
However, there is 2 new worker types G.4X and G.8X
Affected Resource(s) and/or Data Source(s)
aws_glue_job
Potential Terraform Configuration
No response
References
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/glue_job
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: