Skip to content
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

AWS: Switch from containerProperties to ecsProperties #5096

Open
ewels opened this issue Jun 28, 2024 · 2 comments · May be fixed by #5391
Open

AWS: Switch from containerProperties to ecsProperties #5096

ewels opened this issue Jun 28, 2024 · 2 comments · May be fixed by #5391
Assignees

Comments

@ewels
Copy link
Member

ewels commented Jun 28, 2024

According to @delagoya we need to change this ASAP:

I don't know who needs to hear this, but:

If you use AWS Batch, you should default to using the new ecsProperties parameter for all your job definitions. Migrate any past job definition to a new version that moves from containerProperties

Otherwise you are going to Experience Bij later when you have to submit jobs with overrides and forget where in the API those overrides go, depending on the job definition

See also: #4979 where this was a requirement for supporting ipcMode.

NB also the proposed move to Java SDKv2 (#4741), though this shouldn't be required for this switch according to #4979 (comment)

@pditommaso
Copy link
Member

@bentsherman
Copy link
Member

@tom-seqera let's discuss this one tomorrow or Friday, I think it would be a good issue to introduce you to the AWS integration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants