-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
New Resource: aws_glue_job #4028
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from one minor comment that can probably be ignored :)
MaxItems: 1, | ||
Elem: &schema.Resource{ | ||
Schema: map[string]*schema.Schema{ | ||
"max_concurrent_runs": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to have this in an execution_property
block property instead of having max_concurrent_runs
at the top level like max_retries
is?
Just to match the API? A potential for more options in execution_property
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to match the API 😄 We've gotten bitten in the past by colliding attribute names. https://docs.aws.amazon.com/sdk-for-go/api/service/glue/#CreateJobInput
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Valid! Good thing to keep in mind then.
This has been released in version 1.15.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
Hi guys, thank you so much to all of you for your hard work on the glue job we are using it across our datalakes and we love it! One question, there is no reference to the SecurityConfiguration option on the provider and I was wondering if this is going to be left out of scope. This is important for the scenario where the bucket policy enforces encryption and the glue job tries to write unencrypted, it will fail. Thank you! @bflad |
Hi @hugoalmeida17, please create a new Feature Request issue, thanks! |
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! |
Closes #3877