AWS Cloud Resource Utils - Library (ACRU-L)

Pronounced Ah-crew-el (ə-kroo͞′l)

An open source framework for collecting and reusing AWS CDK constructs and stacks.

NOTE: This project is currently not stable (alpha releases only) and is subject change at any time. Please use at your own risk.

Usage: ACRU-L Action

This action provisions AWS stacks given an ACRU-L configuration file. The intention is to encapsulate the code needed to provision resources without conflating application code with devops requirements.

The goal is to avoid conflating microservice application code with "infrastructure as code".

Inputs

subcommand

Optional The aws-cdk subcommand to run. Default "deploy -f --require-approval=never".

Example usage

- user: actions/setup-python@v2
  with:
  python-version: 3.8
- uses: actions/setup-node@v2
  with:
  node-version: 12
- uses: quadio-media/acru-l@1.0.0a4
  with:
    subcommand: deploy -f
  env:
    AWS_REGION: us-east-1
    AWS_ACCOUNT_ID: ${{ secrets.AWS_ACCOUNT_ID }}
    AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
    AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
    DEPLOY_ID: ${{ github.sha }}
    ACRUL_CONFIG_PATH: "./acru-l.toml"

Configuration

The following settings must be passed as environment variables as shown in the example. Sensitive information, especially AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, should be set as encrypted secrets — otherwise, they'll be public to anyone browsing your repository's source code and CI logs.

License

This project is distributed under the MIT license.

Why?

The problem with infrastructure as code ...

Monorepos... Snowflake code...

Confounding application source code with devops

A strict interface and reuse patterns

Installation

poetry add -D acru-l

pip install acru-l

About

Core Concepts

• Resources - Extended constructs
• Services - Collections of Resources that build a service interface
• Stacks - Collections of Services

Resources

Extended constructs with set defaults

Services

TBD

Stacks

TBD