Escape hatches: Go Lang Support

[toyotest2]

Describe the feature

Request: Escape hatches: Go Lang Support

I could not find any Go language samples in the documentation below.
https://docs.aws.amazon.com/cdk/v2/guide/cfn_layer.html

Additionally, I found the following comments at the workshop.

https://catalog.us-east-1.prod.workshops.aws/workshops/d93fec4c-fb0f-4813-ac90-758cb5527f2f/en-US/walkthrough/go/sample/source-construct/s3-bucket

CDK has a concept called the [escape hatch ](https://docs.aws.amazon.com/cdk/latest/guide/cfn_layer.html)
, which allows you to modify an L2 construct's underlying CFN Resource to access features that are supported by CloudFormation but not yet supported by CDK. Unfortunately, CDK for Go does not yet support this functionality, so we have to create the resource through the L1 construct. See [this GitHub issue ](https://github.com/aws/jsii/issues/2819)
for more information and to follow progress on support for CDK escape hatches in Go.

Use Case

For Customize L2/L3 Constructs in Go Lang.

Proposed Solution

No response

Other Information

No response

Acknowledgements

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

CDK version used

2.162.1

Environment details (OS name and version, etc.)

Cloud9AmazonLinux2023-2024-10-21T21-56

[khushail]

Hi @toyotest2 , thanks for reaching out and linking the related docs available. I found this issue mentioned in the workshop doc which was further fixed by the PR.

Considering the usecase, it would be helpful to have the mentioned support for GO as well. Marking the issue as P2 as L2 constructs are available. P2 would mean it would not be immediately addressed by the team but would be on their radar.

[gshpychka]

Although I'm very surprised that missing Go support for L1 would be a P2 issue (considering there's no workaround), L1 resources are fully supported in Go as far as I understand, and escape hatches work with jsii.UnsafeCast. Am I missing something?

[khushail]

Hi @gshpychka , I understand your point of view here. I marked it as P2 as escape hatches are available in other languages and I am not sure supporting this for GO is on the team roadmap.

I would reach out to team on this if they have this in their future action items or something to be considered a priority.