@peterwoodworth Since batch is an experimental module, I wonder if we should just remove the containerOverrides option entirely (since that was what was done on the batch side). Perhaps we can expose those properties as an alternative to containerOverrides

I had considered that @kaizen3031593, and actually went with deprecating the properties at first in exchange for what you proposed - but since this change is within the stepfunctions-tasks module I had decided to stick with the easier change at first to see what you would say.

Still, since this change is within a stable module that would require deprecation instead of outright removal, right?

Whoops I thought this was in batch. My bad, you're right.

Let me know if you'd like me to go with deprecation 👍🏻

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
• Commit ID: 556a26a
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).