Closed brian-mulier-p closed 2 months ago
Hi @brian-mulier-p This is a feature request to the service, I'll raise it internally to the AWS Batch team.
Moving this to the cross-SDK repo aws/aws-sdk
for tracking.
P125826078
@brian-mulier-p the Batch team replied and said it's a feature they are interested in implementing. They've added a feature task to their backlog but don't have a timeline to share for the fix.
Closing this, as there's nothing pending on the SDK team.
This issue is now closed.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
@debora-ito Thank you, I was unaware it was a not a SDK limitation. Is there a link, an issue, something to track this ?
Unfortunately no, there's no mechanisms to track Batch service-side feature requests that are open to the public. I recommend keeping an eye on the changelog but it's not super practical.
Describe the feature
Ability to specify for a container the working directory to use
Use Case
I have a usecase where I need to bootstrap multiple containers where one will eventually fetch from S3 to some job-wide volume and the main container will need to have access to these files.
However both containers are not necessarily using the same image so I'm unable to know where to mount files if I can't specify an arbitrary working directory.
Proposed Solution
No response
Other Information
No response
Acknowledgements
AWS Java SDK version used
2.25.14
JDK version used
17
Operating System and version
Ubuntu