DEPRECATION NOTICE: The
aws-prototyping-sdkis on path to deprecation. This package is simply a wrapper around the individual@aws-prototyping-skd/*packages and has no unique code aside from bundling the other packages. Due to lack of significant value compared to maintenance overhead, this package will be deprecated soon in favor of using the individual packages directly. Please use the individual packages starting now to prevent future migration and loss of update capabilities.
The aws-prototyping-sdk provides stable CDK and Projen constructs, allowing developers to have access to higher level abstractions than provided by the CDK or Projen alone.
For detailed documentation, please refer to the documentation website.
Bundling
This package simply bundles various packages from the @aws-prototyping-sdk namespace which have been marked as stable. As such, not all constructs or classes may be exported from this package and will need to be explicitly imported by creating a dependency on the individual packages.
To illustrate, at the time of writing the following individual packages are published:
@aws-prototyping-sdk
|_ pipeline : [stable]
|_ nx-monorepo : [stable]
|_ static-website : [experimental]
|_ identity : [experimental]
The aws-prototyping-sdk package will bundle all stable packages and export them as namespaces as follows:
aws-prototyping-sdk
|_ pipeline
|_ nx_monorepo
This means if you wanted to access the PDKPipeline which is a stable construct, you simply add a dependency on the aws-prototyping-sdk and import it as follows:
import { nx_monorepo, pipeline } from "aws-prototyping-sdk";
To import experimental constructs, a dependency on the individual package is required. In the case of static-website, a dependency on @aws-prototyping-sdk/static-website is required. The constructs can then be imported as follows:
import { StaticWebsite } from "@aws-prototyping-sdk/static-website";
Metadata
Release files for aws-prototyping-sdk 0.17.5
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 | |
|---|---|---|---|---|
| aws_prototyping_sdk-0.17.5.tar.gz | 8.0 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aws_prototyping_sdk-0.17.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.0 MB
Release files / aws_prototyping_sdk-0.17.5.tar.gz
| Download URL | aws_prototyping_sdk-0.17.5.tar.gz |
|---|---|
| Size | 8.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76285cc3446c8c9188c067b7b0ef7e7f874bd1d1f1736e958f009f6d522e1bdc
|
|
BLAKE2b-256 checksum How to use checksums |
1a0aa1ce37bfbe8aa35c0e467c6b099d28e0e4fb5560a16cf4d8e53b61f4fb02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / aws_prototyping_sdk-0.17.5-py3-none-any.whl
| Download URL | aws_prototyping_sdk-0.17.5-py3-none-any.whl |
|---|---|
| Size | 8.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
efd345d06e0eb345b4090c13add7c128e9dbd1e312dc0ea04d314467fb7b1611
|
|
BLAKE2b-256 checksum How to use checksums |
fbd068036799cc5995d209dc22a4927e7e2e9cbdc9d77402aec31661118ec036
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for aws-prototyping-sdk 0.17.5
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.