diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-nameless-deploy-tools.spec | 523 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 525 insertions, 0 deletions
@@ -0,0 +1 @@ +/nameless-deploy-tools-1.299.tar.gz diff --git a/python-nameless-deploy-tools.spec b/python-nameless-deploy-tools.spec new file mode 100644 index 0000000..6eb66e1 --- /dev/null +++ b/python-nameless-deploy-tools.spec @@ -0,0 +1,523 @@ +%global _empty_manifest_terminate_build 0 +Name: python-nameless-deploy-tools +Version: 1.299 +Release: 1 +Summary: Tools for deploying to AWS via CloudFormation and Serverless framework that support a pull request based workflow +License: Apache 2.0 +URL: http://github.com/NitorCreations/nameless-deploy-tools +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/9f/b5/368bc6691ca1ca3289fe352c7202cb11b94daa753cd79b18f69bbc64c26e/nameless-deploy-tools-1.299.tar.gz +BuildArch: noarch + +Requires: python3-argcomplete +Requires: python3-boto3 +Requires: python3-cloudformation-utils +Requires: python3-configparser +Requires: python3-ec2-utils +Requires: python3-ipaddr +Requires: python3-jmespath +Requires: python3-nitor-vault +Requires: python3-pyaml +Requires: python3-pycryptodomex +Requires: python3-Pygments +Requires: python3-pyOpenSSL +Requires: python3-pyotp +Requires: python3-pyqrcode +Requires: python3-dateutil +Requires: python3-PyYAML +Requires: python3-requests +Requires: python3-scandir +Requires: python3-six +Requires: python3-termcolor +Requires: python3-pypiwin32 +Requires: python3-win-unicode-console +Requires: python3-wmi +Requires: python3-black +Requires: python3-flake8 +Requires: python3-isort +Requires: python3-pip-tools +Requires: python3-pyupgrade +Requires: python3-ruff +Requires: python3-coverage +Requires: python3-mock +Requires: python3-pytest-cov +Requires: python3-pytest-mock +Requires: python3-pytest + +%description +# Nameless Deploy Tools + +[](https://app.travis-ci.com/github/NitorCreations/nameless-deploy-tools/) +[](https://coveralls.io/github/NitorCreations/nameless-deploy-tools?branch=master) +[](https://github.com/psf/black) + +## Released version 1.299 + +Nameless deploy tools are a set of tools to implement a true Infrastructure As Code workflow +with various cloud infrastructure management tools. Currently supported tools are +CloudFormation, AWS CDK, Serverless Framework, Terraform, Azure Resource Manager (with +a YAML syntax) and Bicep. + +## Why Nameless? + +A common analogy for cloud infrastructure has been to move from having pets with +names that need lots of looking after, to cattle that has at most id's. It's time +to move to the industrial age from the agrarian era. The infrastructure our +applications runs now comes and goes, and we know at most some statistical information +about the actual executions. Run times, memory usage, used bandwidth and the like. +We no longer know even the id's of the things that actually run the code. Hence - +nameless. + +## Rationale + +We at Nitor are software engineers with mostly a developer or architect background, but +a lot of us have had to work closely with various Operations teams around the world. +DevOps has a natural appeal to us and immediately "infrastructure as code" meant for us +that we should apply the best development practices to infrastructure development. It starts +with version control and continues with testing new features in isolation and a workflow +that supports this. Our teams usually take into use a feature branch workflow if it is +feasible, and we expect all the tools and practices to support this. For infrastructure +this type of branching means that you should be able to spin up enough of the infrastructure +to be able to verify the changes you want to implement in production. Also, the testing +environment should be close enough to the target environment for the results to be valid. +So the differences between testing and production environments should be minimized and +reviewable. + +With the popular tools like Ansible, Terraform, Chef etc. you need to come up with and +implement the ways to achieve the goals above. As far as I know, no tool besides ndt +has at its core a thought-out way of a branching infrastructure development model. + +## What it is + +nameless-deploy-tools works by defining _Amazon Machine Images_, _[Docker containers](https://www.docker.com)_, +_[Serverless services](https://serverless.com)_ and deploying _[CloudFormation](https://aws.amazon.com/cloudformation/) +stacks_ of resources. CloudFormation stacks can also be defined with _[AWS CDK](https://awslabs.github.io/aws-cdk/)_ +applications. All of the above can also be deployed using _[Terraform](https://www.terraform.io)_. + +## Installation + +```shell +pip install nameless-deploy-tools +``` + +Requires Python 3.7 or newer. + +## Getting started + +To use nameless-deploy-tools you need to set up a _project repository_ that +describes the images you want to build, and the stacks you want to deploy them in. See +[ndt-project-template](https://github.com/NitorCreations/ndt-project-template) +for an example. + +Here are few commands you can use. All of these are run in your project repository root. +You need to have AWS credentials for command line access set up. + +* To bake a new version of an image: `ndt bake-image <image-name>` +* To build a new Docker container image `ndt bake-docker <component> <docker-name>` +* To deploy a stack: + * with a known AMI id: `ndt deploy-stack <image-name> <stack-name> <AMI-id>` + * with the newest AMI id by a given bake job: `ndt deploy-stack <image-name> <stack-name> "" <bake-job-name>` +* To undeploy a stack: `ndt undeploy-stack <image-name> <stack-name>` + +For full list of commands see [here](docs/commands.md) + +You can additionally use a faster register-complete by running `./faster_register_complete.sh`. +This compiles a C++ program from the file [nameless-dt-register-complete.cpp](n_utils/nameless-dt-register-complete.cpp), +and replaces the Python version of `nameless-dt-register-complete` with it. + +## Documentation + +* [Command Reference](docs/commands.md) +* [ndt workspace tooling](docs/workspace.md) +* [Template Pre-Processing](docs/template-processing.md) +* [Multifactor Authentication](docs/mfa.md) +* [Common parameters](docs/parameters.md) + +## Versioning + +This library uses a simplified semantic versioning scheme: major version change for changes +that are not backwards compatible (not expecting these) and the minor +version for all backwards compatible changes. We won't make the distinction between +new functionality and bugfixes, since we don't think it matters and is not a thing +worth wasting time on. We will release often and if we need changes that are not comptatible, +we will fork the next major version and release alphas versions of that until we are +happy to release the next major version and try and have a painless upgrade path. + +## Dependencies + +Python dependencies are specified in [setup.cfg](./setup.cfg). +[pip-compile](https://github.com/jazzband/pip-tools/) is used to generate the `requirements.txt` file. +To update the requirements, use the following commands: + +```shell +pip install --upgrade pip-tools +pip-compile setup.py +``` + +## Code formatting and linting + +This project uses [Black](https://github.com/psf/black) together with [isort](https://github.com/PyCQA/isort) for Python code formatting, +and [flake8](https://github.com/PyCQA/flake8) for linting. +They are configured with a custom line length limit of 120. + +Usage: + +```shell +pip install --upgrade black isort flake8 +black . +isort . +flake8 . +``` + +These can also be integrated to IDEs / editors or run as a pre-commit hook. +See the documentation for example for Black [here](https://black.readthedocs.io/en/stable/integrations/editors.html). +VS Code has built-in support for [Black](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter), +[isort](https://marketplace.visualstudio.com/items?itemName=ms-python.isort), +and [flake8](https://marketplace.visualstudio.com/items?itemName=ms-python.flake8) through official plugins. + +Using with [pre-commit](https://pre-commit.com/): + +```shell +# setup to be run automatically on git commit +pre-commit install + +# run manually +pre-commit run --all-files +``` + + +%package -n python3-nameless-deploy-tools +Summary: Tools for deploying to AWS via CloudFormation and Serverless framework that support a pull request based workflow +Provides: python-nameless-deploy-tools +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-nameless-deploy-tools +# Nameless Deploy Tools + +[](https://app.travis-ci.com/github/NitorCreations/nameless-deploy-tools/) +[](https://coveralls.io/github/NitorCreations/nameless-deploy-tools?branch=master) +[](https://github.com/psf/black) + +## Released version 1.299 + +Nameless deploy tools are a set of tools to implement a true Infrastructure As Code workflow +with various cloud infrastructure management tools. Currently supported tools are +CloudFormation, AWS CDK, Serverless Framework, Terraform, Azure Resource Manager (with +a YAML syntax) and Bicep. + +## Why Nameless? + +A common analogy for cloud infrastructure has been to move from having pets with +names that need lots of looking after, to cattle that has at most id's. It's time +to move to the industrial age from the agrarian era. The infrastructure our +applications runs now comes and goes, and we know at most some statistical information +about the actual executions. Run times, memory usage, used bandwidth and the like. +We no longer know even the id's of the things that actually run the code. Hence - +nameless. + +## Rationale + +We at Nitor are software engineers with mostly a developer or architect background, but +a lot of us have had to work closely with various Operations teams around the world. +DevOps has a natural appeal to us and immediately "infrastructure as code" meant for us +that we should apply the best development practices to infrastructure development. It starts +with version control and continues with testing new features in isolation and a workflow +that supports this. Our teams usually take into use a feature branch workflow if it is +feasible, and we expect all the tools and practices to support this. For infrastructure +this type of branching means that you should be able to spin up enough of the infrastructure +to be able to verify the changes you want to implement in production. Also, the testing +environment should be close enough to the target environment for the results to be valid. +So the differences between testing and production environments should be minimized and +reviewable. + +With the popular tools like Ansible, Terraform, Chef etc. you need to come up with and +implement the ways to achieve the goals above. As far as I know, no tool besides ndt +has at its core a thought-out way of a branching infrastructure development model. + +## What it is + +nameless-deploy-tools works by defining _Amazon Machine Images_, _[Docker containers](https://www.docker.com)_, +_[Serverless services](https://serverless.com)_ and deploying _[CloudFormation](https://aws.amazon.com/cloudformation/) +stacks_ of resources. CloudFormation stacks can also be defined with _[AWS CDK](https://awslabs.github.io/aws-cdk/)_ +applications. All of the above can also be deployed using _[Terraform](https://www.terraform.io)_. + +## Installation + +```shell +pip install nameless-deploy-tools +``` + +Requires Python 3.7 or newer. + +## Getting started + +To use nameless-deploy-tools you need to set up a _project repository_ that +describes the images you want to build, and the stacks you want to deploy them in. See +[ndt-project-template](https://github.com/NitorCreations/ndt-project-template) +for an example. + +Here are few commands you can use. All of these are run in your project repository root. +You need to have AWS credentials for command line access set up. + +* To bake a new version of an image: `ndt bake-image <image-name>` +* To build a new Docker container image `ndt bake-docker <component> <docker-name>` +* To deploy a stack: + * with a known AMI id: `ndt deploy-stack <image-name> <stack-name> <AMI-id>` + * with the newest AMI id by a given bake job: `ndt deploy-stack <image-name> <stack-name> "" <bake-job-name>` +* To undeploy a stack: `ndt undeploy-stack <image-name> <stack-name>` + +For full list of commands see [here](docs/commands.md) + +You can additionally use a faster register-complete by running `./faster_register_complete.sh`. +This compiles a C++ program from the file [nameless-dt-register-complete.cpp](n_utils/nameless-dt-register-complete.cpp), +and replaces the Python version of `nameless-dt-register-complete` with it. + +## Documentation + +* [Command Reference](docs/commands.md) +* [ndt workspace tooling](docs/workspace.md) +* [Template Pre-Processing](docs/template-processing.md) +* [Multifactor Authentication](docs/mfa.md) +* [Common parameters](docs/parameters.md) + +## Versioning + +This library uses a simplified semantic versioning scheme: major version change for changes +that are not backwards compatible (not expecting these) and the minor +version for all backwards compatible changes. We won't make the distinction between +new functionality and bugfixes, since we don't think it matters and is not a thing +worth wasting time on. We will release often and if we need changes that are not comptatible, +we will fork the next major version and release alphas versions of that until we are +happy to release the next major version and try and have a painless upgrade path. + +## Dependencies + +Python dependencies are specified in [setup.cfg](./setup.cfg). +[pip-compile](https://github.com/jazzband/pip-tools/) is used to generate the `requirements.txt` file. +To update the requirements, use the following commands: + +```shell +pip install --upgrade pip-tools +pip-compile setup.py +``` + +## Code formatting and linting + +This project uses [Black](https://github.com/psf/black) together with [isort](https://github.com/PyCQA/isort) for Python code formatting, +and [flake8](https://github.com/PyCQA/flake8) for linting. +They are configured with a custom line length limit of 120. + +Usage: + +```shell +pip install --upgrade black isort flake8 +black . +isort . +flake8 . +``` + +These can also be integrated to IDEs / editors or run as a pre-commit hook. +See the documentation for example for Black [here](https://black.readthedocs.io/en/stable/integrations/editors.html). +VS Code has built-in support for [Black](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter), +[isort](https://marketplace.visualstudio.com/items?itemName=ms-python.isort), +and [flake8](https://marketplace.visualstudio.com/items?itemName=ms-python.flake8) through official plugins. + +Using with [pre-commit](https://pre-commit.com/): + +```shell +# setup to be run automatically on git commit +pre-commit install + +# run manually +pre-commit run --all-files +``` + + +%package help +Summary: Development documents and examples for nameless-deploy-tools +Provides: python3-nameless-deploy-tools-doc +%description help +# Nameless Deploy Tools + +[](https://app.travis-ci.com/github/NitorCreations/nameless-deploy-tools/) +[](https://coveralls.io/github/NitorCreations/nameless-deploy-tools?branch=master) +[](https://github.com/psf/black) + +## Released version 1.299 + +Nameless deploy tools are a set of tools to implement a true Infrastructure As Code workflow +with various cloud infrastructure management tools. Currently supported tools are +CloudFormation, AWS CDK, Serverless Framework, Terraform, Azure Resource Manager (with +a YAML syntax) and Bicep. + +## Why Nameless? + +A common analogy for cloud infrastructure has been to move from having pets with +names that need lots of looking after, to cattle that has at most id's. It's time +to move to the industrial age from the agrarian era. The infrastructure our +applications runs now comes and goes, and we know at most some statistical information +about the actual executions. Run times, memory usage, used bandwidth and the like. +We no longer know even the id's of the things that actually run the code. Hence - +nameless. + +## Rationale + +We at Nitor are software engineers with mostly a developer or architect background, but +a lot of us have had to work closely with various Operations teams around the world. +DevOps has a natural appeal to us and immediately "infrastructure as code" meant for us +that we should apply the best development practices to infrastructure development. It starts +with version control and continues with testing new features in isolation and a workflow +that supports this. Our teams usually take into use a feature branch workflow if it is +feasible, and we expect all the tools and practices to support this. For infrastructure +this type of branching means that you should be able to spin up enough of the infrastructure +to be able to verify the changes you want to implement in production. Also, the testing +environment should be close enough to the target environment for the results to be valid. +So the differences between testing and production environments should be minimized and +reviewable. + +With the popular tools like Ansible, Terraform, Chef etc. you need to come up with and +implement the ways to achieve the goals above. As far as I know, no tool besides ndt +has at its core a thought-out way of a branching infrastructure development model. + +## What it is + +nameless-deploy-tools works by defining _Amazon Machine Images_, _[Docker containers](https://www.docker.com)_, +_[Serverless services](https://serverless.com)_ and deploying _[CloudFormation](https://aws.amazon.com/cloudformation/) +stacks_ of resources. CloudFormation stacks can also be defined with _[AWS CDK](https://awslabs.github.io/aws-cdk/)_ +applications. All of the above can also be deployed using _[Terraform](https://www.terraform.io)_. + +## Installation + +```shell +pip install nameless-deploy-tools +``` + +Requires Python 3.7 or newer. + +## Getting started + +To use nameless-deploy-tools you need to set up a _project repository_ that +describes the images you want to build, and the stacks you want to deploy them in. See +[ndt-project-template](https://github.com/NitorCreations/ndt-project-template) +for an example. + +Here are few commands you can use. All of these are run in your project repository root. +You need to have AWS credentials for command line access set up. + +* To bake a new version of an image: `ndt bake-image <image-name>` +* To build a new Docker container image `ndt bake-docker <component> <docker-name>` +* To deploy a stack: + * with a known AMI id: `ndt deploy-stack <image-name> <stack-name> <AMI-id>` + * with the newest AMI id by a given bake job: `ndt deploy-stack <image-name> <stack-name> "" <bake-job-name>` +* To undeploy a stack: `ndt undeploy-stack <image-name> <stack-name>` + +For full list of commands see [here](docs/commands.md) + +You can additionally use a faster register-complete by running `./faster_register_complete.sh`. +This compiles a C++ program from the file [nameless-dt-register-complete.cpp](n_utils/nameless-dt-register-complete.cpp), +and replaces the Python version of `nameless-dt-register-complete` with it. + +## Documentation + +* [Command Reference](docs/commands.md) +* [ndt workspace tooling](docs/workspace.md) +* [Template Pre-Processing](docs/template-processing.md) +* [Multifactor Authentication](docs/mfa.md) +* [Common parameters](docs/parameters.md) + +## Versioning + +This library uses a simplified semantic versioning scheme: major version change for changes +that are not backwards compatible (not expecting these) and the minor +version for all backwards compatible changes. We won't make the distinction between +new functionality and bugfixes, since we don't think it matters and is not a thing +worth wasting time on. We will release often and if we need changes that are not comptatible, +we will fork the next major version and release alphas versions of that until we are +happy to release the next major version and try and have a painless upgrade path. + +## Dependencies + +Python dependencies are specified in [setup.cfg](./setup.cfg). +[pip-compile](https://github.com/jazzband/pip-tools/) is used to generate the `requirements.txt` file. +To update the requirements, use the following commands: + +```shell +pip install --upgrade pip-tools +pip-compile setup.py +``` + +## Code formatting and linting + +This project uses [Black](https://github.com/psf/black) together with [isort](https://github.com/PyCQA/isort) for Python code formatting, +and [flake8](https://github.com/PyCQA/flake8) for linting. +They are configured with a custom line length limit of 120. + +Usage: + +```shell +pip install --upgrade black isort flake8 +black . +isort . +flake8 . +``` + +These can also be integrated to IDEs / editors or run as a pre-commit hook. +See the documentation for example for Black [here](https://black.readthedocs.io/en/stable/integrations/editors.html). +VS Code has built-in support for [Black](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter), +[isort](https://marketplace.visualstudio.com/items?itemName=ms-python.isort), +and [flake8](https://marketplace.visualstudio.com/items?itemName=ms-python.flake8) through official plugins. + +Using with [pre-commit](https://pre-commit.com/): + +```shell +# setup to be run automatically on git commit +pre-commit install + +# run manually +pre-commit run --all-files +``` + + +%prep +%autosetup -n nameless-deploy-tools-1.299 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-nameless-deploy-tools -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.299-1 +- Package Spec generated @@ -0,0 +1 @@ +7adc72f6f500f56b0b7f0f8d5ffcffb9 nameless-deploy-tools-1.299.tar.gz |