JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 5
  • Score
    100M100P100Q18702F
  • License GPL-3.0-or-later

Package Exports

  • @envtio/base
  • @envtio/base/lib/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@envtio/base) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Base

[!NOTE] A set of base CDKTF constructs to use in Environment Toolkit specs.

The purpose is to build handcrafted, AWS CDK like, DevX on top of the L0 @cdktf/provider-aws resources.

Restrictions

[!IMPORTANT] An AwsBeacon can only be created within an AwsSpec.

An AwsSpec is limited to a single AWS Account/Region

This allows a close mapping between environment-toolkit specs for AWS and AWS CDK concepts, simplifying configuration at a trade-off for more complicated multi stack orchestration managed by the environment-toolkit.

For each target AWS Account and Region (defined as "Environment"), you must define a separate AwsSpec in the same way AWS CDK Stacks are limited to a single Environment.

Due to this, the AwsSpec has a single terraform aws provider configuration which must be provided in its constructor.

Also, alias configuration of the Terraform provider has been stripped out.

Due to JSII Typescript Restrictions upstream @cdktf/provider-aws.provider.AwsProviderConfig is programatically modified via ./projenrc/aws-provider-struct-builder for future maintenance.

Resource Identifiers are managed by et

To decouple identities from discoverability, all resource identifiers must be provided by the environment toolkit CLI.