aws-batch JobDefinition: Support import using 'fromJobDefinitionName'

Currently JobDefinition constructs only supports fromJobDefinitionArn. For using Batch in StepFunctions, we can provide JobDefinition as any one of name, name:revision or ARN (Ref)

Now to import JobDefinition in StepFunctions, we can only use fromJobDefinitionArn which is not flexible since JobDefinitionArn contains the revision as well. This leads to an ARN update after every change in revision (very frequent). The ideal way to handle this would be to import using name instead of the ARN

Hence a method like fromJobDefinitionName would suit this particular use case.

Use Case

Proposed Solution

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[ayush987goyal]

@iliapolo What I was trying to refer to in the issue was:

Consider the scenario where the JobDefinition is maintained in a different stack altogether. It has its own lifecycle of code changes and the version is bumped every now and then. We want to use the latest version of the this JobDefinition is another stack for StepFunctions.

To achieve this, let’s say we made a stack export of JobDefinitionArn from the JobDefinition stack and then used it in StepFunctions stack using:

JobDefinition.fromJobDefinitionArn(arn)

Now, when there is a code change and version updates for the JobDefinition, it changes the the ARN (since ARN contains version number). This leads to deployment failure for the JobDefinition stack since it would say the export is currently used in another stack (StepFunctions stack). To resolve this, we would have to remove the reference of that export from the StepFunctions stack and then redeploy. We have to do this for every code change in JobDefinition.

To prevent this issue, StepFunction for Batch supports passing only the JobDefinitionName as well. But this is currently not possible since to import a JobDefinition from one stack to another, it only supports fromJobDefinitionArn. Therefore we would probably need fromJobDefinitionName in Batch.

I hope it was clear.

[ayush987goyal]

Added a PR https://github.com/aws/aws-cdk/pull/10448 to close this issue.