Python 3.6 and 3.7 language support for the CloudFormation CLI
The CloudFormation CLI (cfn) allows you to author your own resource providers that can be used by CloudFormation.
This plugin library helps to provide Python runtime bindings for the execution of your providers by CloudFormation.
The CloudFormation Resource Provider Development Kit (RPDK) allows you to author your own resource providers that can be used by CloudFormation.
This plugin library helps to provide runtime bindings for the execution of your providers by CloudFormation.
Join us on Discord! Connect & interact with CloudFormation developers & experts, find channels to discuss and get help for our CLIs, cfn-lint, CloudFormation registry, StackSets, Guard and more:
pip install cloudformation-cli-python-plugin
$ cfn init
Initializing new project
What's the name of your resource type?
(Organization::Service::Resource)
>> Foo::Bar::Baz
Select a language for code generation:
[1] java
[2] csharp
[3] python36
[4] python37
(enter an integer):
>> 4
Use docker for platform-independent packaging (Y/n)?
This is highly recommended unless you are experienced
with cross-platform Python packaging.
>> y
Initialized a new project in <>
$ cfn submit --dry-run
$ cat <<EOT > test.json
{
"credentials": {
"accessKeyId": "",
"secretAccessKey": "",
"sessionToken": ""
},
"action": "CREATE",
"request": {
"clientRequestToken": "ecba020e-b2e6-4742-a7d0-8a06ae7c4b2b",
"desiredResourceState": {
"Title": "This_Is_The_Title_For_My_Example",
"TestCode": "NOT_STARTED"
},
"previousResourceState": null,
"logicalResourceIdentifier": null
},
"callbackContext": null
}
EOT
$ sam local invoke TestEntrypoint --event test.json
For changes to the plugin, a Python virtual environment is recommended. The development requirements can be sourced from the core repository:
python3 -m venv env
source env/bin/activate
pip install -e . -e src/ \
-r https://raw.githubusercontent.com/aws-cloudformation/aws-cloudformation-rpdk/master/requirements.txt
pre-commit install
Linting and running unit tests is done via pre-commit, and so is performed automatically on commit. The continuous integration also runs these checks. Manual options are available so you don't have to commit):
# run all hooks on all files, mirrors what the CI runs
pre-commit run --all-files
# run unit tests only. can also be used for other hooks, e.g. black, flake8, pylint-local
pre-commit run pytest-local
This library is licensed under the Apache 2.0 License.