Metadata-Version: 2.1
Name: stackuchin
Version: 1.0.0
Summary: CLI for Stackuchin - Automatically create, update and delete AWS CloudFormation stacks in multiple AWS accounts and regions at the same time
Home-page: https://github.com/Rungutan/stackuchin
Author: Rungutan
Author-email: support@rungutan.com
License: UNKNOWN
Download-URL: https://github.com/Rungutan/stackuchin/archive/1.0.0.tar.gz
Project-URL: Bug Reports, https://github.com/Rungutan/stackuchin/issues
Project-URL: Source, https://github.com/Rungutan/stackuchin/
Description: # stackuchin
        
        ## What is Stackuchin?
        
        It's a CLI tool developed by [Rungutan](https://rungutan.com) and designed to automatically create, update and delete CloudFormation stacks in multiple AWS accounts and regions at the same time.
        
        
        ## Why use the CLI?
        
        This CLI has been designed for:
        1) versioning AWS CloudFormation parameters in GIT
        2) deploying to multiple AWS accounts or AWS regions either in PARALLEL or SEQUENTIAL
        3) send notifications to Slack channels with AWS errors based on operation
        4) support **create**, **update** and **delete** commands
        5) can be ran either manually or through a pipeline definition in your CI/CD system
        6) supports both AWS normal CloudFormation templates as well AWS SAM templates
        7) supports parent/child stacks
        8) it supports NoEcho parameters
        9) it supports tagging of resources at stack level
        10) it supports unattended deployment (through a CI/CD system)
        
        And this is just the tip of the iceberg...
        
        ## What can this CLI NOT do?
        
        Unfortunately, it cannot understand contracted forms of verbs in AWS CloudFormation.
        
        In short, you'll have to rename `!If` commands to `Fn::If`.
        
        ## Is it production ready?
        
        We, at [Rungutan](https://rungutan.com), in order to support global concurrency for load testing and ensure high availability as well, have around 200 stacks on average deployed in each and every of the 15 regions our platform currently supports.
        
        In short, yes, we use **Stackuchin** to handle updates for around 3000 AWS CloudFormation stacks.
        
        And no, we're not exagerating or bumping the numbers :-)
        
        ## What are the normal use cases?
        
        If simply the fact that you can now git-version all your stacks AND their stack parameters, isn't enough, then:
        * your developers can now manage AWS CloudFormation stack themselves, WITHOUT needing to have any "write" IAM permissions
        * you can use CI/CD for automated deployments
        * you can use pull requests to review parameter/stack changes
        
        ## How to install the CLI?
        
        ```shell script
        pip install stackuchin
        ```
        
        ## How to run the CLI?
        
        * Check the overall help menu
        
        ```shell script
        $ stackuchin help
        
        usage: stackuchin <command> [<args>]
        
        To see help text, you can run:
            stackuchin help
            stackuchin version
            stackuchin create --help
            stackuchin delete --help
            stackuchin update --help
            stackuchin pipeline --help
        
        CLI tool to automatically create, update and delete AWS CloudFormation stacks in multiple AWS accounts and regions at the same time
        
        positional arguments:
          command     Command to run
        
        optional arguments:
          -h, --help  show this help message and exit
        
        ```
        
        * Check the help menu for a specific command
        
        ```shell script
        $ stackuchin create --help
        
        usage: stackuchin [-h] [--stack_file STACK_FILE] --stack_name STACK_NAME [--secret Parameter=Value] [--slack_webhook SLACK_WEBHOOK] [--s3_bucket S3_BUCKET] [--s3_prefix S3_PREFIX] [-p PROFILE]
        
        Create command system
        
        optional arguments:
          -h, --help            show this help message and exit
          --stack_file STACK_FILE
                                The YAML file which contains your stack definitions.
                                Defaults to "./cloudformation-stacks.yaml" if not specified.
          --stack_name STACK_NAME
                                The stack that you wish to create
          --secret Parameter=Value
                                Argument used to specify values for NoEcho parameters in your stack
          --slack_webhook SLACK_WEBHOOK
                                Argument used to overwrite environment variable STACKUCHIN_SLACK.
                                If argument is specified, any notifications will be sent to this URL.
                                If not specified, the script will check for env var STACKUCHIN_SLACK.
                                If neither argument nor environment variable is specified, then no notifications will be sent.
          --s3_bucket S3_BUCKET
                                Argument used to overwrite environment variable STACKUCHIN_BUCKET_NAME.
                                If argument is specified, then the template is first uploaded here before used in the stack.
                                If not specified, the script will check for env var STACKUCHIN_BUCKET_NAME.
                                If neither argument nor environment variable is specified, then the script will attempt to feed the template directly to the AWS API call, however, due to AWS CloudFormation API call limitations, you might end up with a bigger template in byte size than the max value allowed by AWS.
                                Details here -> https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cloudformation-limits.html
          --s3_prefix S3_PREFIX
                                Argument used to overwrite environment variable STACKUCHIN_BUCKET_PREFIX.
                                The bucket prefix path to be used when the S3 bucket is defined.
          -p PROFILE, --profile PROFILE
                                The AWS profile you'll be using.
                                If not specified, the "default" profile will be used. 
                                If no profiles are defined, then the default AWS credential mechanism starts.
        
        ```
        
Keywords: stackuchin stackuchin-cli stackuchin_cli cli aws cloudformation stacks deployment integrationcotinuous continuos devops tools
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Information Technology
Classifier: Intended Audience :: System Administrators
Classifier: Topic :: Software Development :: Testing
Classifier: Topic :: Software Development :: Quality Assurance
Classifier: Topic :: Software Development :: Testing :: Acceptance
Classifier: Topic :: Software Development :: Testing :: BDD
Classifier: Topic :: Software Development :: Testing :: Mocking
Classifier: Topic :: Software Development :: Testing :: Traffic Generation
Classifier: Topic :: Software Development :: Testing :: Unit
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3 :: Only
Requires-Python: >=3.5, <4
Description-Content-Type: text/markdown
Provides-Extra: test
