Toolset to render and manage AWS CloudFormation ( )
Go to file
Stefan Reimer 7d6135e099
ZeroDownTime/CloudBender/pipeline/head This commit looks good Details
fix: code style / flake8 automation
2022-02-22 11:04:29 +01:00
cloudbender fix: code style / flake8 automation 2022-02-22 11:04:29 +01:00
tests First release on PyPy, Makefile and License 2019-02-07 22:05:33 +00:00
.flake8 fix: code style / flake8 automation 2022-02-22 11:04:29 +01:00
.gitignore Initial checkin 2018-11-22 18:31:59 +00:00 feat: add DISABLE_SOPS 2021-10-13 13:23:31 +02:00
Dockerfile ci: add git to build container to make versioning work 2022-02-08 17:08:09 +01:00
Jenkinsfile ci: disable trivy fail for now 2022-02-08 16:19:48 +01:00 First release on PyPy, Makefile and License 2019-02-07 22:05:33 +00:00
Makefile fix: code style / flake8 automation 2022-02-22 11:04:29 +01:00 chore: some more docs 2021-11-15 18:37:52 +01:00
cloudbender.png Update logo 2020-05-27 14:05:08 +01:00
dev-requirements.txt feat: Enabled Jinja2 V3 support 2022-01-26 13:27:07 +01:00
requirements.txt feat: Enabled Jinja2 V3 support 2022-01-26 13:27:07 +01:00
setup.cfg ci: use version number from Git tag 2022-02-08 16:01:41 +01:00 ci: further versioning tweaks 2022-02-08 16:52:05 +01:00

Logo CloudBender


Toolset to deploy and maintain infrastructure in automated and trackable manner.
First class support for:


$ pip install cloudbender

State management


All state is handled by AWS Cloudformation.
The required account and region are determined by CloudBender automatically from the configuration.


The state for all Pulumi resources are stored on S3 in your account and in the same region as the resources being deployed. No data is send to nor shared with the official Pulumi provided APIs.

CloudBender configures Pulumi with a local, temporary workspace on the fly. This incl. the injection of various common parameters like the AWS account ID and region etc.


Usage: cloudbender [OPTIONS] COMMAND [ARGS]...

  --version   Show the version and exit.
  --debug     Turn on debug logging.
  --dir TEXT  Specify cloudbender project directory.
  --help      Show this message and exit.

  clean              Deletes all previously rendered files locally
  create-change-set  Creates a change set for an existing stack - CFN only
  create-docs        Parses all documentation fragments out of rendered...
  delete             Deletes stacks or stack groups
  get-config         Get a config value, decrypted if secret
  outputs            Prints all stack outputs
  preview            Preview of Pulumi stack up operation
  provision          Creates or updates stacks or stack groups
  refresh            Refreshes Pulumi stack / Drift detection
  render             Renders template and its parameters - CFN only
  set-config         Sets a config value, encrypts with stack key if secret
  sync               Renders template and provisions it right away
  validate           Validates already rendered templates using cfn-lint...

Config management

  • Within the config folder each directory represents either a stack group if it has sub-directories, or an actual Cloudformation stack in case it is a leaf folder.
  • The actual configuration for each stack is hierachly merged. Lower level config files overwrite higher-level values. Complex data structures like dictionaries and arrays are deep merged.



Secrets handling


CloudBender supports the native Pulumi secret handling. See Pulumi Docs for details.


CloudBender supports SOPS to encrypt values in any config yaml file since version 0.8.1

If a sops encrypted config file is detected CloudBender will automatically try to decrypt the file during execution.
All required information to decrypt has to be present in the embedded sops config or set ahead of time via sops supported ENVIRONMENT variables.

SOPS support can be disabled by setting DISABLE_SOPS in order to reduce timeouts etc.