batch: aws-cdk-go: case-insensitive file name collision with CfnJobDefinition_EFSVolumeConfigurationProperty.go

[fabiolanfranchi]

Please add your +1 👍 to let us know you have encountered this

Status: IN-PROGRESS

Overview:

Due to some changes in AWS Batch service CFN schema, and renaming in some types, the generated L1 classes for these types have conflicts in names that will cause issues in case insensitive systems.

Complete Error Message:

Go reports a case-insensitive file name collision when I run `go get github.com/aws/aws-cdk-go/awscdk/[email protected]`. The conflict is caused by [awsbatch/CfnJobDefinition_EFSVolumeConfigurationProperty.go](https://github.com/aws/aws-cdk-go/blob/awscdk/v2.174.0/awscdk/awsbatch/CfnJobDefinition_EFSVolumeConfigurationProperty.go) and [awsbatch/CfnJobDefinition_EfsVolumeConfigurationProperty.go](https://github.com/aws/aws-cdk-go/blob/awscdk/v2.174.0/awscdk/awsbatch/CfnJobDefinition_EfsVolumeConfigurationProperty.go).

Workaround:

Revert aws-cdk-lib to version 2.173.4 or less.

Solution:

The team will patch a new release (2.174.1) that contains a fix for this issue.

---

Original Issue

Describe the bug

I use aws-cdk-go and I'm trying to upgrade from v2.173.4 to v2.174.0 on macOS with the default case-insensitive file system (APFS).

Go reports a case-insensitive file name collision when I run go get github.com/aws/aws-cdk-go/awscdk/[email protected]. The conflict is caused by awsbatch/CfnJobDefinition_EFSVolumeConfigurationProperty.go and awsbatch/CfnJobDefinition_EfsVolumeConfigurationProperty.go.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

2.173.4

Expected Behavior

go get github.com/aws/aws-cdk-go/awscdk/[email protected] should succeed on case-insensitive file systems.

Current Behavior

The command fails and the dependency is not updated in go.mod.

% go get github.com/aws/aws-cdk-go/awscdk/[email protected]
go: downloading github.com/aws/aws-cdk-go/awscdk/v2 v2.174.0
go: github.com/aws/aws-cdk-go/awscdk/[email protected]: create zip: awsbatch/CfnJobDefinition_EfsVolumeConfigurationProperty.go: case-insensitive file name collision: "awsbatch/CfnJobDefinition_EFSVolumeConfigurationProperty.go" and "awsbatch/CfnJobDefinition_EfsVolumeConfigurationProperty.go"

Reproduction Steps

On macOS with case-insensitive APFS run go get github.com/aws/aws-cdk-go/awscdk/[email protected].

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.174.0 (build 9604329)

Framework Version

No response

Node.js Version

22.12.0

OS

macOS 15.2

Language

Go

Language Version

1.23.4

Other information

No response

[krokoko]

Facing the same issue here: https://github.com/awslabs/generative-ai-cdk-constructs/actions/runs/12635568484/job/35206496533

[ashishdhingra]

Looks like in CDK documentation as well, we have definition for 2 interfaces:

• EfsVolumeConfigurationProperty
• EFSVolumeConfigurationProperty

Easily reproducible using below commands (in a new directory):

• npm install -g [email protected]
• cdk init app --language go
• go get

This gives error:

go: github.com/aws/aws-cdk-go/awscdk/[email protected]: verifying go.mod: github.com/aws/aws-cdk-go/awscdk/[email protected]/go.mod: reading https://sum.golang.org/lookup/github.com/aws/aws-cdk-go/awscdk/[email protected]: 404 Not Found
	server response: not found: create zip: awsbatch/CfnJobDefinition_EfsVolumeConfigurationProperty.go: case-insensitive file name collision: "awsbatch/CfnJobDefinition_EFSVolumeConfigurationProperty.go" and "awsbatch/CfnJobDefinition_EfsVolumeConfigurationProperty.go"

[moelasmar]

new CDK lib got released (V2.174.1), and the aws-cdk-go library looks good.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.