Patch for AWS CDK 1.81.0
The @aws-cdk/aws-eks and @aws-cdk/aws-s3-deployment modules are broken in
v1.81.0 of the AWS CDK due to a missing file in the npm bundle.
Tracking issue: https://github.com/aws/aws-cdk/issues/12291
We apologize for this. Until we are able to release a patch, you can use this tool to apply a patch to the relevant modules. This patch will only work if you are using v1.81.0 and will need to get removed in the future.
You can apply this patch in all supported CDK programming languages:
JavaScript/TypeScript
See example.
Install using npm/yarn:
npm install awscdk-81-patch
Add this to your main file (before the App construct is created):
# Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826
from awscdk_81_patch import Patch
Patch.apply()
app = cdk.App()
Python
See example.
Add this to your requirements.txt:
awscdk-81-patch
Install:
pip install -r requirements.txt
Add this to your app.py:
from awscdk_81_patch import Patch
Patch.apply()
app = core.App()
# ...
Java
Add this to your pom.xml file:
<dependencies>
<dependency>
<groupId>com.github.eladb</groupId>
<artifactId>awscdk-81-patch</artifactId>
<version>LATEST</version>
</dependency>
</dependencies>
Apply first thing in your main() method:
import com.github.eladb.awscdk81patch.Patch;
public static void main(final String[] args) { {
Patch.apply();
App app = new App();
// ...
}
.NET
Install this module:
cd src/MyProject # go to where your .csproj file resides
dotnet add package Eladb.AwsCdk81Patch
In Program.cs, add this:
using Eladb.AwsCdk81Patch;
public static void Main(string[] args)
{
Patch.Apply();
var app = new App();
// ...
}
License
Distributed under the Apache 2.0 license.
Metadata
Release files for awscdk-81-patch 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| awscdk-81-patch-1.1.1.tar.gz | 16.9 kB | Without provenance | Details for awscdk-81-patch-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| awscdk_81_patch-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for awscdk_81_patch-1.1.1-py3-none-any.whl |
Total release size: 33.8 kB
Release files / awscdk-81-patch-1.1.1.tar.gz
| Download URL | awscdk-81-patch-1.1.1.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28eedea37f8d8d6249bfcc1e05efbb6e9d5b3217ae3561cace7e442c79a56c1b
|
|
BLAKE2b-256 checksum How to use checksums |
ef9c0c0cc8682cf6de650a459e5f75bc54d336a5c52adc1f2f0c3adb85c4c068
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.0 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.9
|
Release files / awscdk_81_patch-1.1.1-py3-none-any.whl
| Download URL | awscdk_81_patch-1.1.1-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92ec52fceb8a8d3127c847c6e10df12789fd5449760aaabdd80ba6df259acf62
|
|
BLAKE2b-256 checksum How to use checksums |
72158dc95119f197defdd05593279929707ae99285ce7edfb1fcd3ac063b283b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.0 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.9
|
Security for awscdk-81-patch 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.