AWS Codepipeline Creator
Features
aws-pipeline-creator creates a aws codepipeline cloudformation stack, and points to a build specifical file in the code repository
Installation
aws-pipeline-creator is on PyPI so all you need is:
$ pip install aws-pipeline-creator
Example
Getting help
$ pipeline-creator upsert --help
Usage: pipeline-creator upsert [OPTIONS]
primary function for creating a bucket :return:
Options:
-v, --version TEXT code version
-d, --dryrun dry run
-y, --yaml YAML template (deprecated - YAMLness is now detected at
run-time
--no-poll Start the stack work but do not poll
-i, --ini TEXT INI file with needed information [required]
--debug Turn on debugging
--help Show this message and exit.
pipeline-creator upsert -i config/my.ini
Example Ini file
[environment]
# This is a general bucket where the cloudformation template will be uploaded to prior to deployment
bucket = cloudformation-templates
# The name you want on the cloudformation stack
stack_name = my-stack-name
region = us-east-1
profile = my-aws-profile
[tags]
# These are the tags which will be automatically applied to resources
Name = test-codepipeline
ResourceOwner = my_boss
Project = MyCoolProject
DeployedBy = me
[parameters]
# CodeCommit repository name
RepositoryName = repo_name
# Codecommit repository branch name
RepositoryBranchName = master
# A project name or code
Project = test
ProjectDescription = test
# The role which is utilized for the code pipeline, see below for an example role policy
BuildServiceRole = arn:aws:iam::123456789:role/AWSCodebuildRole
BuildProjectName = MyBuild
Subnets = subnet-c1234556
SecurityGroups = sg-123456
Timeout = 60
# The location in the repository where the build spec file is located
BuildspecFile = folder/buildspec.yml
# Set the environment code. This is how developers code deployments in the build spec.
# If EnvCode = dev, then do this, if EnvCode is prod, then do that
EnvironmentCode = dev
VpcId = vpc-123456
# This is a bucket where the builds from each stage in the build process are stored
DeploymentBucketName = codepipeline-deployments
# The image to utilize
# You can also use default AWS images from https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html
# Example: Image = aws/codebuild/docker:17.09.0
Image = 123456789.dkr.ecr.us-east-1.amazonaws.com/codepipeline:latest
[meta-parameters]
# These are the metadata parameters which are applied to the template via jinja2
ProjectName = myproject
Demonstration
Metadata
Release files for aws-pipeline-creator 0.0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aws_pipeline_creator-0.0.9.tar.gz | 8.4 kB | Without provenance | Details for aws_pipeline_creator-0.0.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_pipeline_creator-0.0.9-py2-none-any.whl | Python 2 | none | any | Details for aws_pipeline_creator-0.0.9-py2-none-any.whl |
Total release size: 17.3 kB
Release files / aws_pipeline_creator-0.0.9.tar.gz
| Download URL | aws_pipeline_creator-0.0.9.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
747e0d1f6f3ce3e27170067dc2d6b0d06dd4c34a9085718c8a033ac2a62e04c6
|
|
BLAKE2b-256 checksum How to use checksums |
828b803863f0428f0a898871efc9fd61f20657f80aa1942ec9840f2ba28ba300
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.1.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/2.7.10
|
Release files / aws_pipeline_creator-0.0.9-py2-none-any.whl
| Download URL | aws_pipeline_creator-0.0.9-py2-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
ed1abc40c7e02dcfa2567eef8839a95552fbc56fd11efde66cf125883f550f8e
|
|
BLAKE2b-256 checksum How to use checksums |
91cb4cab10e86b6975145c1db098d9ef779d7c5405a48c2b1f62cdf2f9b54518
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.1.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/2.7.10
|
Security for aws-pipeline-creator 0.0.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.