-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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]: Add support for additional Batch EKS Pod Properties #38606
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/batch
Issues and PRs that pertain to the batch service.
Comments
danquack
added
the
enhancement
Requests to existing resources that expand the functionality or scope.
label
Jul 30, 2024
github-actions
bot
added
the
service/batch
Issues and PRs that pertain to the batch service.
label
Jul 30, 2024
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
terraform-aws-provider
bot
added
the
needs-triage
Waiting for first response or review from a maintainer.
label
Jul 30, 2024
danquack
changed the title
[Enhancement]: Add support for additional EKS Pod Properties
[Enhancement]: Add support for additional Batch EKS Pod Properties
Jul 30, 2024
justinretzolk
removed
the
needs-triage
Waiting for first response or review from a maintainer.
label
Jul 31, 2024
Good catch @justinretzolk. Missed that in the schema scroll. I'll remove that pull secret, but the other ones still needs attention. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/batch
Issues and PRs that pertain to the batch service.
Description
Some additional attributes were added to eksProperties:
Affected Resource(s) and/or Data Source(s)
aws_batch_job_definition
Potential Terraform Configuration
References
https://docs.aws.amazon.com/batch/latest/APIReference/API_EksPodProperties.html
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: