Metadata-Version: 2.1
Name: terraform-worker
Version: 0.7.2
Summary: An orchestration tool for Terraform
Home-page: https://github.com/ephur/terraform-worker
Author: Richard Maynard
Author-email: richard.maynard@gmail.com
License: UNKNOWN
Description: # terraform-worker
        
        `terraform-worker` is a command line tool for pipelining terraform operations while sharing state between them. The worker consumese a yaml configuration file which is broken up into two sections, definitions (which were really just top level modules) and sub-modules. The definitions are put into a worker config in order, with the terraform variables, and remote state variables.  Following is a sample configuration file and command:
        
        *./worker.yaml*
        ```yaml
        terraform:
          providers:
            aws:
              vars:
                region: //aws-region//
                version: "~> 2.61"
        
          # global level variables
          terraform_vars:
            region: //aws-region//
            environment: dev
        
          definitions:
            # Either setup a VPC and resources, or deploy into an existing one
            network:
              path: /definitions/aws/network-existing
        
            database:
              path: /definitions/aws/rds
        
          plugins:
            aws:
              version: 2.61.0
        ```
        
        ```sh
        % worker --aws-profile default --backend s3 terraform --show-output example1
        ```
        
        ## Development
        
        ```sh
         # virtualenv setup stuf... and then:
         % pip install poetry && make init
        ```
        
        ## Background
        
        The terraform worker was a weekend project to run terraform against a series of definitions (modules). The idea was the configuration vars, provider configuration, remote state, and variables from remote state would all be dynamically generated. The purpose was for building kubernetes deployments, and allowing all of the configuration information to be stored as either yamnl files in github, or have the worker configuration generated by an API which stored all of the deployment configurations in a database.
        
Platform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: System Administrators
Classifier: Intended Audience :: Information Technology
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Natural Language :: English
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3.8
Classifier: Topic :: System :: Systems Administration
Requires-Python: >=3.6
Description-Content-Type: text/markdown
