| Name | infrable JSON |
| Version |
0.1.40
JSON |
| download |
| home_page | None |
| Summary | Hanny's legendary infrastructure as code solution. |
| upload_time | 2024-09-25 06:56:45 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.10 |
| license | Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. |
| keywords |
declarative
infrastructure
management
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# Infrable
Hanny's legendary infrastructure as code solution.
[](https://pypi.org/project/infrable)
```bash
# Install
pip install -U infrable # requires python >= 3.10
# Bootstrap a new project
infrable init
```
# Table of contents
1. [Prologue](#prologue)
2. [Chapter 1 - Chaos](#chapter-1---chaos)
3. [Chapter 2 - Hosts and Services](#chapter-2---hosts-and-services)
4. [Chapter 3 - Templates](#chapter-3---templates)
5. [Chapter 4 - The Deploy or Recover Workflow](#chapter-4---the-deploy-or-recover-workflow)
6. [Chapter 5 - Commands, Tasks and Workflows](#chapter-5---commands,-tasks-and-workflows)
7. [Chapter 6 - Environments and Switches](#chapter-6---environments-and-switches)
8. [Chapter 7 - Meta and Secrets](#chapter-7---meta-and-secrets)
9. [Chapter 8 - Custom Modules](#chapter-8---custom-modules)
## Prologue
In an infinite void surrounded by blinking lights, Hanny woke up with her memory hollow,
only her name echoing in the dark corners of her mind. She found herself floating in a
realm between the tangible world of **Python** code and the ethereal cosmos of the space. A
synthetic voice resonated around her about a crucial **infrastructure** migration project
but it was all Greek to her. Her memory, once the key to the Python kingdom, failed to
provide any answers. She was stuck in an interstellar labyrinth, entrusted with a
technology mission she could not recall, her only anchors being a mechanical keyboard and
lines of code whizzing past on the nearby screen.
## Chapter 1 - Chaos
In the void of her discontent, Hanny started to recall fragments of a past life: back on
Earth, where a looming infrastructure migration project threatened to upend everything.
Humanity grappled with a **chaotic infrastructure** and an **ill-prepared toolkit**. Python
developers fought with convoluted tools, while the desperate search for **declarative
configuration management** proved futile. Amidst this disarray, Hanny was catapulted into
the cosmos, a reluctant knight tasked with an unenviable quest: to find an
**uncomplicated yet competent solution** capable of taming this looming catastrophe.
## Chapter 2 - Hosts and Services
In a moment of revelation, Hanny grasped the intricacies of infrastructure: **hosts and the
services** they housed, the vital backbone of any system. She understood the criticality of
maintaining **a single reference source, a complete, harmonious documentation capturing
these elemental relationships**. Committing herself to uphold this single source of truth
principle, she began the painstaking process of documentation, pouring every detail into
a consolidated testament christened **"infra.py"**.
**infra.py**
```python
from infrable import Host, Service
# Hosts/ -----------------------------------------------------------------------
dev_host = Host(fqdn="dev.example.com", ip="127.0.0.1")
beta_host = Host(fqdn="beta.example.com", ip="127.0.0.1")
prod_host = Host(fqdn="prod.example.com", ip="127.0.0.1")
# /Hosts -----------------------------------------------------------------------
# Services/ --------------------------------------------------------------------
dev_web = Service(host=dev_host, port=8080)
beta_web = Service(host=beta_host, port=8080)
prod_web = Service(host=prod_host, port=8080)
dev_nginx = Service(host=dev_host, port=80)
beta_nginx = Service(host=beta_host, port=80)
prod_nginx = Service(host=prod_host, port=80)
# /Services --------------------------------------------------------------------
```
List the hosts and services:
```bash
infrable hosts
infrable services
```
## Chapter 3 - Templates
Gradually piecing together her fragmented memories, Hanny realized configuration files
for the host deployments ought to be maintained as **templates, drawing values as
needed from "infra.py"**. Back on Earth, the challenge had been a lack of a coherent
system to document the destination of these files, a problem of organization that posed a
significant hurdle. Then, in a moment of genius, Hanny conceived a groundbreaking
solution. She'd document the files' path directly within the configuration templates
themselves. And so, with renewed vigor, she started adding crucial details as **header
comments nestled within the configuration files**, a legendary stroke promising to
transform the face of infrastructure migration.
**infra.py**
```python
template_prefix = "https://github.com/username/repository/blob/main"
```
**templates/nginx/web.j2**
```nginx
# vim: syn=nginx
# ---
# src: {{ template_prefix }}/{{ _template.src }}
# dest: {{ dev_nginx.host }}:/etc/nginx/sites-enabled/web
# chmod: 644
# chown: root:root
# ---
server {
listen {{ dev_nginx.port }};
listen [::]:{{ dev_nginx.port }}
server_name {{ dev_nginx.host.fqdn }} www.{{ dev_nginx.host.fqdn }};
location / {
proxy_pass http://127.0.0.1:{{ dev_web.port }};
include proxy_params;
}
}
```
NOTE: The `_template.src` is a special variable, available in all templates.
## Chapter 4 - The Deploy or Recover Workflow
In the vast expanse of uncertainty, one thing became crystal clear to Hanny: the
importance of **reviewing the files made through "infra.py" and comparing these with the
currently deployed configurations before pushing them**. This process would intercept
any **live changes** and ensure their inclusion in the templates. Her cautious nature also
recognized the essential function of maintaining **local backups** of the utilized
configurations, providing an insurance of sorts. To address any complications, she
conceived a failsafe measure: **The Deploy or Recover Workflow**. It promised relief from
human error while ensuring an approach to **easily revert and recover** the service,
another triumphant stride in Hanny’s cosmic saga.
Deploy workflow:
```bash
infrable files deploy [path]
## Same as
# infrable files gen [path]
# infrable files pull
# infrable files backup
# infrable files push
```
For snake folks:
```python
from infrable import files
files.deploy(path)
## Same as
# files.gen(path)
# files.pull()
# files.backup()
# files.push()
```
```mermaid
flowchart TD;
A[gen: generate artifacts from templates and infra.py as .new files] --> B[pull: for each generated artifact pull the currently deployed version from server as .old files];
B --> C[backup: copy the artifacts in a local backup directory for easy recovery in case of failure];
C --> E[diff: compare the .new and .old files];
E -- push: for each result --> F{is there any difference?};
F -- yes --> H[display the diff];
F -- no --> G[skip and delete artifacts];
H --> I{confirm push?};
I -- yes --> J[push the file onto the server];
I -- no --> K[skip and delete artifacts];
```
Diff example:
```diff
--- .infrable/files/root@dev.example.com/etc/monit/conf.d/system.cfg.old
+++ .infrable/files/root@dev.example.com/etc/monit/conf.d/system.cfg.new
@@ -1,13 +1,14 @@
check system dev.example.com
- if memory usage > 85% then alert
+ # if memory usage > 85% then alert
if cpu usage (user) > 80% for 3 cycles then alert
if cpu usage (system) > 80% for 3 cycles then alert
Push? (y, n, all) [y]:
```
Recover workflow:
```bash
infrable files recover [path]
## Same as
# infrable files revert [path]
# infrable files push
```
For snake folks:
```python
from infrable import files
files.recover(path)
## Same as
# files.revert(path)
# files.push()
```
```mermaid
flowchart TD;
A[revert: copy the artifacts from the given or latest backup directory into artifacts directory but in reverse order] --> B[diff: compare the .new and .old files];
B --> C[push: run the steps for the push workflow]
```
## Chapter 5 - Commands, Tasks and Workflows
As Hanny delved deeper into the complexities of infrastructure migration, she encountered
a critical realization: the need to extend beyond mere configuration pushing. To attain a
seamless transition, testing, service restarts, and other post-deployment actions were
imperative. With relentless determination, she integrated a feature within "infra.py" to
**execute remote commands** on hosts, a capability enhancing the deployment process.
```bash
# Run a command on a host by name
infrable remote dev_host "sudo systemctl reload nginx"
# Or by service name
infrable remote dev_nginx "sudo systemctl reload nginx"
# Or all affected hosts (as per files diff)
infrable remote affected-hosts "sudo systemctl reload nginx"
# Or
infrable files affected-hosts | infrable remote - "sudo systemctl reload nginx"
```
But Hanny's pursuit of excellence didn't halt there; she grasped the inadequacy of loose
command execution, acknowledging the necessity for structured organization. Thus, she
envisioned a novel concept - the creation of **"Tasks"**, groups of related commands
designed to streamline operations.
**infra.py**
```python
import typer
# Tasks/ -----------------------------------------------------------------------
dev_nginx.typer = typer.Typer(help="dev_nginx specific tasks.")
@dev_nginx.typer.command(name="reload")
def reload_dev_nginx():
"""[TASK] Reload nginx: infrable dev-nginx reload"""
assert dev_nginx.host, "Service must have a host to reload"
dev_nginx.host.remote().sudo.nginx("-t")
dev_nginx.host.remote().sudo.systemctl.reload.nginx()
# /Tasks -----------------------------------------------------------------------
```
Running tasks:
```bash
infrable dev-nginx reload
```
As she toiled to realize this vision, a brilliant idea swept over her - to
orchestrate these tasks into coherent sequences, she christened them
**"workflows"**, heralding the dawn of a new era in infrastructure management.
**infra.py**
```python
from infrable import concurrent, paths
# Workflows/ -----------------------------------------------------------------------
deploy = typer.Typer(help="Deployment workflows.")
@deploy.command(name="dev-nginx")
def deploy_dev_nginx():
"""[WORKFLOW] Deploy dev_nginx files: infrable deploy dev-nginx"""
files.deploy(paths.templates / "nginx")
cmd = "sudo nginx -t && sudo systemctl reload nginx && echo success || echo failed"
fn = lambda host: (host, host.remote().sudo(cmd))
for host, result in concurrent(fn, files.affected_hosts()):
print(f"{host}: {result}")
# /Workflows -----------------------------------------------------------------------
```
Running workflows:
```bash
infrable deploy dev-nginx
```
## Chapter 6 - Environments and Switches
The exhilaration of progress was swiftly countered by the rigors of defining **templates,
tasks, and workflows independently for every host within multiple environments**. Hanny's
keen eyes blinked tiredly at lines of Python code, her fingers aching from relentless
typing. It was then that she stumbled upon another vital realization: **the service and
host relationship hinged upon the environment**. The environment — "dev", "beta", "prod",
among others — determined where services were deployed. Wondering **if environments could
be switchable**, she pondered a pivotal question: What if the "infra.py" file could
adjust values based on the environment? This would phenomenally simplify the deployment
process, **utilizing the same template, task, and workflow definitions across different
hosts**. Seizing on this insight, Hanny developed **'Switch'**, an ingenious mechanism
allowing **environment-dependent value adjustment within "infra.py"**. With 'Switch',
infrastructure migration wasn't a labyrinth to navigate but a journey of exploration and
innovation. The weight of her mission lightened with every line of code she churned out.
And so Hanny, engulfed by the silence of the cosmos, marched on, her spirit indomitable,
her zeal untamed.
**infra.py**
```python
from infrable import Switch, Host, Service
# Environments/ ----------------------------------------------------------------
dev = "dev"
beta = "beta"
prod = "prod"
environments = {dev, beta, prod}
env = Switch(environments, init=dev) # <-- Defining a switch for different environments
current_env = env()
# /Environments ----------------------------------------------------------------
# Hosts/ -----------------------------------------------------------------------
dev_host = Host(fqdn="dev.example.com", ip="127.0.0.1")
beta_host = Host(fqdn="beta.example.com", ip="127.0.0.2")
prod_host = Host(fqdn="prod.example.com", ip="127.0.0.3")
managed_hosts = env( # <-- Switching hosts based on the environment
dev=[dev_host],
beta=[beta_host],
prod=[prod_host],
)
# /Hosts -----------------------------------------------------------------------
# Services/ --------------------------------------------------------------------
web = Service(
host=env.strict(dev=dev_host, beta=beta_host, prod=prod_host), # <-- Strict switch
port=8080,
)
nginx = Service(port=80, host=web.host) # <-- No need to use switch here
# /Services --------------------------------------------------------------------
```
Updating the templates to use the switchable values:
**templates/nginx/proxy_params.j2**
```nginx
# vim: syn=nginx
# ---
# src: {{ template_prefix }}/{{ _template.src }}
# dest:
# {% for host in managed_hosts %} # <-- Yes, you can
# - loc: {{ host }}:/etc/nginx/proxy_params
# {% endfor %}
# chmod: 644
# chown: root:root
# ---
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
```
Managing switches:
```bash
# Switch current environment
infrable switch env [dev|beta|prod]
# Check the current switch value
infrable switch env
# See other options for the switch
infrable switch env --options
# If you name a switch "env", you get an alias for convenience
infrable env [dev|beta|prod]
# Check all switch values
infrable switches
```
## Chapter 7 - Meta and Secrets
A veil of mystery cloaked Hanny's latest quest. She coveted the ability to access **secret
values, untouched by the eyes of version control systems, and juxtapose these to hosts
and services**. It was a daunting challenge — to embed securely these secret keys within
the Python labyrinth without heightening complexity. She mused, her gaze focused on the
stars scattered across the cosmos. If simplicity was the mother of invention, Hanny would
be its devoted disciple. She engaged in the great **Pythonic tradition of simplicity**,
armed with wisdom acquired from prior challenges, plunging into the task at hand. She
devised an elegant strategy. Her solution was a poet’s dream and a programmer’s delight,
the relief of her achievement echoing in the cosmic silence.
**infra.py**
```python
from infrable import Meta, readfile
common_secret_key = readfile("secrets/common/secret_key") # <-- Read a secret file
web = Service(
meta=Meta(secret_key=common_secret_key), # <-- Attach metadata to items
host=env(dev=dev_host, beta=beta_host, prod=prod_host),
port=8080,
)
```
Managing secrets:
```bash
# Hide secrets from git
echo /secrets/ >> .gitignore
# Update the secrets by hand
vim secrets/common/secret_key
```
## Chapter 8 - Custom Modules
As the celestial silence enveloped her, Hanny stared at the last line of code and
finally, exhaled. The Python maestro had defied the odds, charting a path through the
sprawling galaxy of infrastructure migration. In her hands, humanity held the weapon to
combat the specter of inevitable infrastructure displacement, not just once but
potentially countless times henceforth. No longer would they flounder in the face of
migration, for **'infrable'** was here.
But if the endless cosmos stood as a testament to anything, it was the **limitless
potential for growth**. Hanny, ever the visionary, saw beyond the painstaking creation of
a toolkit. She envisioned a continuously evolving mechanism, a collaborative system
enhanced by the collective genius of Python peers worldwide. That's when it struck her.
Like a supernova in the silent night, she realized the adaptability imbued within Python.
Fellow programmers could craft **Python modules** and stitch them into the existing
"infra.py", thus **extending and elevating its functionality**, a synergy of skills and
codes enhancing 'infrable' to uncharted territories.
**modules/mycloud.py**
```python
from dataclasses import dataclass
from typer import Typer
from infrable import Host, infra
@dataclass
class MyCloud:
"""MyCloud Python library."""
secret_api_key: str
typer: Typer | None = None
def provision_ubuntu_host(self, fqdn: str):
ip = self.api.create_ubuntu_host(fqdn)
return MyCloudUbuntuHost(fqdn=fqdn, ip=ip)
@dataclass
class MyCloudUbuntuHost(Host):
"""MyCloud's customized Ubuntu server."""
def setup(self):
self.install_mycloud_agent()
def install_mycloud_agent(self):
raise NotImplementedError
workflows = Typer()
@workflows.command()
def provision_ubuntu_host(fqdn: str, setup: bool = True):
"""[WORKFLOW] Provision Ubuntu host."""
# Get the MyCloud instance from infra.py
cloud = next(iter(infra.item_types[MyCloud].values()))
# Provision the host
host = cloud.provision_ubuntu_host(fqdn)
if setup:
host.setup()
name = fqdn.split(".")[0].replace("-", "_")
print("Add the host to the infra.py file.")
print(f"{name} = {repr(host}")
```
Plugging the module in infra.py:
**infra.py**
```python
from modules import mycloud
# Clouds/ ----------------------------------------------------------------------
cloud = mycloud.MyCloud(secret_api_key=readfile("secrets/mycloud/secret_api_key"))
cloud.typer = mycloud.workflows
# /Clouds ----------------------------------------------------------------------
```
Running the module workflows:
```bash
infra cloud --help
```
Raw data
{
"_id": null,
"home_page": null,
"name": "infrable",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": "Arijit Basu <sayanarijit@gmail.com>",
"keywords": "declarative, infrastructure, management",
"author": null,
"author_email": "Arijit Basu <sayanarijit@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/f7/44/606bb4e2b943ea918c92e827311439f34c9fc04287cc401ff730a6e6be09/infrable-0.1.40.tar.gz",
"platform": null,
"description": "# Infrable\n\nHanny's legendary infrastructure as code solution.\n\n[](https://pypi.org/project/infrable)\n\n```bash\n# Install\npip install -U infrable # requires python >= 3.10\n\n# Bootstrap a new project\ninfrable init\n```\n\n# Table of contents\n\n1. [Prologue](#prologue)\n2. [Chapter 1 - Chaos](#chapter-1---chaos)\n3. [Chapter 2 - Hosts and Services](#chapter-2---hosts-and-services)\n4. [Chapter 3 - Templates](#chapter-3---templates)\n5. [Chapter 4 - The Deploy or Recover Workflow](#chapter-4---the-deploy-or-recover-workflow)\n6. [Chapter 5 - Commands, Tasks and Workflows](#chapter-5---commands,-tasks-and-workflows)\n7. [Chapter 6 - Environments and Switches](#chapter-6---environments-and-switches)\n8. [Chapter 7 - Meta and Secrets](#chapter-7---meta-and-secrets)\n9. [Chapter 8 - Custom Modules](#chapter-8---custom-modules)\n\n## Prologue\n\nIn an infinite void surrounded by blinking lights, Hanny woke up with her memory hollow,\nonly her name echoing in the dark corners of her mind. She found herself floating in a\nrealm between the tangible world of **Python** code and the ethereal cosmos of the space. A\nsynthetic voice resonated around her about a crucial **infrastructure** migration project\nbut it was all Greek to her. Her memory, once the key to the Python kingdom, failed to\nprovide any answers. She was stuck in an interstellar labyrinth, entrusted with a\ntechnology mission she could not recall, her only anchors being a mechanical keyboard and\nlines of code whizzing past on the nearby screen.\n\n## Chapter 1 - Chaos\n\nIn the void of her discontent, Hanny started to recall fragments of a past life: back on\nEarth, where a looming infrastructure migration project threatened to upend everything.\nHumanity grappled with a **chaotic infrastructure** and an **ill-prepared toolkit**. Python\ndevelopers fought with convoluted tools, while the desperate search for **declarative\nconfiguration management** proved futile. Amidst this disarray, Hanny was catapulted into\nthe cosmos, a reluctant knight tasked with an unenviable quest: to find an\n**uncomplicated yet competent solution** capable of taming this looming catastrophe.\n\n## Chapter 2 - Hosts and Services\n\nIn a moment of revelation, Hanny grasped the intricacies of infrastructure: **hosts and the\nservices** they housed, the vital backbone of any system. She understood the criticality of\nmaintaining **a single reference source, a complete, harmonious documentation capturing\nthese elemental relationships**. Committing herself to uphold this single source of truth\nprinciple, she began the painstaking process of documentation, pouring every detail into\na consolidated testament christened **\"infra.py\"**.\n\n**infra.py**\n\n```python\nfrom infrable import Host, Service\n\n# Hosts/ -----------------------------------------------------------------------\ndev_host = Host(fqdn=\"dev.example.com\", ip=\"127.0.0.1\")\nbeta_host = Host(fqdn=\"beta.example.com\", ip=\"127.0.0.1\")\nprod_host = Host(fqdn=\"prod.example.com\", ip=\"127.0.0.1\")\n# /Hosts -----------------------------------------------------------------------\n\n\n# Services/ --------------------------------------------------------------------\ndev_web = Service(host=dev_host, port=8080)\nbeta_web = Service(host=beta_host, port=8080)\nprod_web = Service(host=prod_host, port=8080)\n\ndev_nginx = Service(host=dev_host, port=80)\nbeta_nginx = Service(host=beta_host, port=80)\nprod_nginx = Service(host=prod_host, port=80)\n# /Services --------------------------------------------------------------------\n```\n\nList the hosts and services:\n\n```bash\ninfrable hosts\ninfrable services\n```\n\n## Chapter 3 - Templates\n\nGradually piecing together her fragmented memories, Hanny realized configuration files\nfor the host deployments ought to be maintained as **templates, drawing values as\nneeded from \"infra.py\"**. Back on Earth, the challenge had been a lack of a coherent\nsystem to document the destination of these files, a problem of organization that posed a\nsignificant hurdle. Then, in a moment of genius, Hanny conceived a groundbreaking\nsolution. She'd document the files' path directly within the configuration templates\nthemselves. And so, with renewed vigor, she started adding crucial details as **header\ncomments nestled within the configuration files**, a legendary stroke promising to\ntransform the face of infrastructure migration.\n\n**infra.py**\n\n```python\ntemplate_prefix = \"https://github.com/username/repository/blob/main\"\n```\n\n**templates/nginx/web.j2**\n\n```nginx\n# vim: syn=nginx\n\n# ---\n# src: {{ template_prefix }}/{{ _template.src }}\n# dest: {{ dev_nginx.host }}:/etc/nginx/sites-enabled/web\n# chmod: 644\n# chown: root:root\n# ---\n\nserver {\n listen {{ dev_nginx.port }};\n listen [::]:{{ dev_nginx.port }}\n\n server_name {{ dev_nginx.host.fqdn }} www.{{ dev_nginx.host.fqdn }};\n\n location / {\n proxy_pass http://127.0.0.1:{{ dev_web.port }};\n include proxy_params;\n }\n}\n```\n\nNOTE: The `_template.src` is a special variable, available in all templates.\n\n## Chapter 4 - The Deploy or Recover Workflow\n\nIn the vast expanse of uncertainty, one thing became crystal clear to Hanny: the\nimportance of **reviewing the files made through \"infra.py\" and comparing these with the\ncurrently deployed configurations before pushing them**. This process would intercept\nany **live changes** and ensure their inclusion in the templates. Her cautious nature also\nrecognized the essential function of maintaining **local backups** of the utilized\nconfigurations, providing an insurance of sorts. To address any complications, she\nconceived a failsafe measure: **The Deploy or Recover Workflow**. It promised relief from\nhuman error while ensuring an approach to **easily revert and recover** the service,\nanother triumphant stride in Hanny\u2019s cosmic saga.\n\nDeploy workflow:\n\n```bash\ninfrable files deploy [path]\n\n## Same as\n# infrable files gen [path]\n# infrable files pull\n# infrable files backup\n# infrable files push\n```\n\nFor snake folks:\n\n```python\nfrom infrable import files\n\nfiles.deploy(path)\n\n## Same as\n# files.gen(path)\n# files.pull()\n# files.backup()\n# files.push()\n```\n\n```mermaid\nflowchart TD;\n A[gen: generate artifacts from templates and infra.py as .new files] --> B[pull: for each generated artifact pull the currently deployed version from server as .old files];\n B --> C[backup: copy the artifacts in a local backup directory for easy recovery in case of failure];\n C --> E[diff: compare the .new and .old files];\n E -- push: for each result --> F{is there any difference?};\n F -- yes --> H[display the diff];\n F -- no --> G[skip and delete artifacts];\n H --> I{confirm push?};\n I -- yes --> J[push the file onto the server];\n I -- no --> K[skip and delete artifacts];\n```\n\nDiff example:\n\n```diff\n--- .infrable/files/root@dev.example.com/etc/monit/conf.d/system.cfg.old\n\n+++ .infrable/files/root@dev.example.com/etc/monit/conf.d/system.cfg.new\n\n@@ -1,13 +1,14 @@\n\n check system dev.example.com\n- if memory usage > 85% then alert\n+ # if memory usage > 85% then alert\n if cpu usage (user) > 80% for 3 cycles then alert\n if cpu usage (system) > 80% for 3 cycles then alert\n\nPush? (y, n, all) [y]:\n```\n\nRecover workflow:\n\n```bash\ninfrable files recover [path]\n\n## Same as\n# infrable files revert [path]\n# infrable files push\n```\n\nFor snake folks:\n\n```python\nfrom infrable import files\n\nfiles.recover(path)\n\n## Same as\n# files.revert(path)\n# files.push()\n```\n\n```mermaid\nflowchart TD;\n\n A[revert: copy the artifacts from the given or latest backup directory into artifacts directory but in reverse order] --> B[diff: compare the .new and .old files];\n B --> C[push: run the steps for the push workflow]\n```\n\n## Chapter 5 - Commands, Tasks and Workflows\n\nAs Hanny delved deeper into the complexities of infrastructure migration, she encountered\na critical realization: the need to extend beyond mere configuration pushing. To attain a\nseamless transition, testing, service restarts, and other post-deployment actions were\nimperative. With relentless determination, she integrated a feature within \"infra.py\" to\n**execute remote commands** on hosts, a capability enhancing the deployment process.\n\n```bash\n# Run a command on a host by name\ninfrable remote dev_host \"sudo systemctl reload nginx\"\n\n# Or by service name\ninfrable remote dev_nginx \"sudo systemctl reload nginx\"\n\n# Or all affected hosts (as per files diff)\ninfrable remote affected-hosts \"sudo systemctl reload nginx\"\n\n# Or\ninfrable files affected-hosts | infrable remote - \"sudo systemctl reload nginx\"\n```\n\nBut Hanny's pursuit of excellence didn't halt there; she grasped the inadequacy of loose\ncommand execution, acknowledging the necessity for structured organization. Thus, she\nenvisioned a novel concept - the creation of **\"Tasks\"**, groups of related commands\ndesigned to streamline operations.\n\n**infra.py**\n\n```python\nimport typer\n\n# Tasks/ -----------------------------------------------------------------------\ndev_nginx.typer = typer.Typer(help=\"dev_nginx specific tasks.\")\n\n@dev_nginx.typer.command(name=\"reload\")\ndef reload_dev_nginx():\n \"\"\"[TASK] Reload nginx: infrable dev-nginx reload\"\"\"\n\n assert dev_nginx.host, \"Service must have a host to reload\"\n dev_nginx.host.remote().sudo.nginx(\"-t\")\n dev_nginx.host.remote().sudo.systemctl.reload.nginx()\n# /Tasks -----------------------------------------------------------------------\n```\n\nRunning tasks:\n\n```bash\ninfrable dev-nginx reload\n```\n\nAs she toiled to realize this vision, a brilliant idea swept over her - to\norchestrate these tasks into coherent sequences, she christened them\n**\"workflows\"**, heralding the dawn of a new era in infrastructure management.\n\n**infra.py**\n\n```python\nfrom infrable import concurrent, paths\n\n# Workflows/ -----------------------------------------------------------------------\ndeploy = typer.Typer(help=\"Deployment workflows.\")\n\n@deploy.command(name=\"dev-nginx\")\ndef deploy_dev_nginx():\n \"\"\"[WORKFLOW] Deploy dev_nginx files: infrable deploy dev-nginx\"\"\"\n\n files.deploy(paths.templates / \"nginx\")\n cmd = \"sudo nginx -t && sudo systemctl reload nginx && echo success || echo failed\"\n fn = lambda host: (host, host.remote().sudo(cmd))\n for host, result in concurrent(fn, files.affected_hosts()):\n print(f\"{host}: {result}\")\n# /Workflows -----------------------------------------------------------------------\n```\n\nRunning workflows:\n\n```bash\ninfrable deploy dev-nginx\n```\n\n## Chapter 6 - Environments and Switches\n\nThe exhilaration of progress was swiftly countered by the rigors of defining **templates,\ntasks, and workflows independently for every host within multiple environments**. Hanny's\nkeen eyes blinked tiredly at lines of Python code, her fingers aching from relentless\ntyping. It was then that she stumbled upon another vital realization: **the service and\nhost relationship hinged upon the environment**. The environment \u2014 \"dev\", \"beta\", \"prod\",\namong others \u2014 determined where services were deployed. Wondering **if environments could\nbe switchable**, she pondered a pivotal question: What if the \"infra.py\" file could\nadjust values based on the environment? This would phenomenally simplify the deployment\nprocess, **utilizing the same template, task, and workflow definitions across different\nhosts**. Seizing on this insight, Hanny developed **'Switch'**, an ingenious mechanism\nallowing **environment-dependent value adjustment within \"infra.py\"**. With 'Switch',\ninfrastructure migration wasn't a labyrinth to navigate but a journey of exploration and\ninnovation. The weight of her mission lightened with every line of code she churned out.\nAnd so Hanny, engulfed by the silence of the cosmos, marched on, her spirit indomitable,\nher zeal untamed.\n\n**infra.py**\n\n```python\nfrom infrable import Switch, Host, Service\n\n# Environments/ ----------------------------------------------------------------\ndev = \"dev\"\nbeta = \"beta\"\nprod = \"prod\"\n\nenvironments = {dev, beta, prod}\nenv = Switch(environments, init=dev) # <-- Defining a switch for different environments\ncurrent_env = env()\n# /Environments ----------------------------------------------------------------\n\n# Hosts/ -----------------------------------------------------------------------\ndev_host = Host(fqdn=\"dev.example.com\", ip=\"127.0.0.1\")\nbeta_host = Host(fqdn=\"beta.example.com\", ip=\"127.0.0.2\")\nprod_host = Host(fqdn=\"prod.example.com\", ip=\"127.0.0.3\")\n\nmanaged_hosts = env( # <-- Switching hosts based on the environment\n dev=[dev_host],\n beta=[beta_host],\n prod=[prod_host],\n)\n# /Hosts -----------------------------------------------------------------------\n\n# Services/ --------------------------------------------------------------------\nweb = Service(\n host=env.strict(dev=dev_host, beta=beta_host, prod=prod_host), # <-- Strict switch\n port=8080,\n)\n\nnginx = Service(port=80, host=web.host) # <-- No need to use switch here\n# /Services --------------------------------------------------------------------\n```\n\nUpdating the templates to use the switchable values:\n\n**templates/nginx/proxy_params.j2**\n\n```nginx\n# vim: syn=nginx\n\n# ---\n# src: {{ template_prefix }}/{{ _template.src }}\n# dest:\n# {% for host in managed_hosts %} # <-- Yes, you can\n# - loc: {{ host }}:/etc/nginx/proxy_params\n# {% endfor %}\n# chmod: 644\n# chown: root:root\n# ---\nproxy_set_header Host $http_host;\nproxy_set_header X-Real-IP $remote_addr;\nproxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\nproxy_set_header X-Forwarded-Proto $scheme;\n```\n\nManaging switches:\n\n```bash\n# Switch current environment\ninfrable switch env [dev|beta|prod]\n\n# Check the current switch value\ninfrable switch env\n\n# See other options for the switch\ninfrable switch env --options\n\n# If you name a switch \"env\", you get an alias for convenience\ninfrable env [dev|beta|prod]\n\n# Check all switch values\ninfrable switches\n```\n\n## Chapter 7 - Meta and Secrets\n\nA veil of mystery cloaked Hanny's latest quest. She coveted the ability to access **secret\nvalues, untouched by the eyes of version control systems, and juxtapose these to hosts\nand services**. It was a daunting challenge \u2014 to embed securely these secret keys within\nthe Python labyrinth without heightening complexity. She mused, her gaze focused on the\nstars scattered across the cosmos. If simplicity was the mother of invention, Hanny would\nbe its devoted disciple. She engaged in the great **Pythonic tradition of simplicity**,\narmed with wisdom acquired from prior challenges, plunging into the task at hand. She\ndevised an elegant strategy. Her solution was a poet\u2019s dream and a programmer\u2019s delight,\nthe relief of her achievement echoing in the cosmic silence.\n\n**infra.py**\n\n```python\nfrom infrable import Meta, readfile\n\ncommon_secret_key = readfile(\"secrets/common/secret_key\") # <-- Read a secret file\n\nweb = Service(\n meta=Meta(secret_key=common_secret_key), # <-- Attach metadata to items\n host=env(dev=dev_host, beta=beta_host, prod=prod_host),\n port=8080,\n)\n```\n\nManaging secrets:\n\n```bash\n# Hide secrets from git\necho /secrets/ >> .gitignore\n\n# Update the secrets by hand\nvim secrets/common/secret_key\n```\n\n## Chapter 8 - Custom Modules\n\nAs the celestial silence enveloped her, Hanny stared at the last line of code and\nfinally, exhaled. The Python maestro had defied the odds, charting a path through the\nsprawling galaxy of infrastructure migration. In her hands, humanity held the weapon to\ncombat the specter of inevitable infrastructure displacement, not just once but\npotentially countless times henceforth. No longer would they flounder in the face of\nmigration, for **'infrable'** was here.\n\nBut if the endless cosmos stood as a testament to anything, it was the **limitless\npotential for growth**. Hanny, ever the visionary, saw beyond the painstaking creation of\na toolkit. She envisioned a continuously evolving mechanism, a collaborative system\nenhanced by the collective genius of Python peers worldwide. That's when it struck her.\nLike a supernova in the silent night, she realized the adaptability imbued within Python.\nFellow programmers could craft **Python modules** and stitch them into the existing\n\"infra.py\", thus **extending and elevating its functionality**, a synergy of skills and\ncodes enhancing 'infrable' to uncharted territories.\n\n**modules/mycloud.py**\n\n```python\nfrom dataclasses import dataclass\nfrom typer import Typer\nfrom infrable import Host, infra\n\n@dataclass\nclass MyCloud:\n \"\"\"MyCloud Python library.\"\"\"\n\n secret_api_key: str\n typer: Typer | None = None\n\n def provision_ubuntu_host(self, fqdn: str):\n ip = self.api.create_ubuntu_host(fqdn)\n return MyCloudUbuntuHost(fqdn=fqdn, ip=ip)\n\n@dataclass\nclass MyCloudUbuntuHost(Host):\n \"\"\"MyCloud's customized Ubuntu server.\"\"\"\n\n def setup(self):\n self.install_mycloud_agent()\n\n def install_mycloud_agent(self):\n raise NotImplementedError\n\nworkflows = Typer()\n\n@workflows.command()\ndef provision_ubuntu_host(fqdn: str, setup: bool = True):\n \"\"\"[WORKFLOW] Provision Ubuntu host.\"\"\"\n\n # Get the MyCloud instance from infra.py\n cloud = next(iter(infra.item_types[MyCloud].values()))\n\n # Provision the host\n host = cloud.provision_ubuntu_host(fqdn)\n if setup:\n host.setup()\n\n name = fqdn.split(\".\")[0].replace(\"-\", \"_\")\n print(\"Add the host to the infra.py file.\")\n print(f\"{name} = {repr(host}\")\n```\n\nPlugging the module in infra.py:\n\n**infra.py**\n\n```python\nfrom modules import mycloud\n\n# Clouds/ ----------------------------------------------------------------------\ncloud = mycloud.MyCloud(secret_api_key=readfile(\"secrets/mycloud/secret_api_key\"))\ncloud.typer = mycloud.workflows\n# /Clouds ----------------------------------------------------------------------\n```\n\nRunning the module workflows:\n\n```bash\ninfra cloud --help\n```\n",
"bugtrack_url": null,
"license": "Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License. \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\" \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"[]\" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.",
"summary": "Hanny's legendary infrastructure as code solution.",
"version": "0.1.40",
"project_urls": {
"Homepage": "https://github.com/stckme/infrable"
},
"split_keywords": [
"declarative",
" infrastructure",
" management"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "7c25a5dcd6b594119493c5ad3647cf51cd469c8e0397311ba1d12ccc6d967d1f",
"md5": "ab96d4ffc9b2446114d31df09a5596e1",
"sha256": "d2c66d4a546c9a65df48513c78e6a9b440b6bec9d89f30772412b506edbb06ff"
},
"downloads": -1,
"filename": "infrable-0.1.40-py3-none-any.whl",
"has_sig": false,
"md5_digest": "ab96d4ffc9b2446114d31df09a5596e1",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 31644,
"upload_time": "2024-09-25T06:56:34",
"upload_time_iso_8601": "2024-09-25T06:56:34.703435Z",
"url": "https://files.pythonhosted.org/packages/7c/25/a5dcd6b594119493c5ad3647cf51cd469c8e0397311ba1d12ccc6d967d1f/infrable-0.1.40-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "f744606bb4e2b943ea918c92e827311439f34c9fc04287cc401ff730a6e6be09",
"md5": "de268def11a14b41881d6a436dd91b2b",
"sha256": "63082ce7dd53fa048ee127d80d8ca0cf49f8444ff942fc7bf278bf42f1d4619d"
},
"downloads": -1,
"filename": "infrable-0.1.40.tar.gz",
"has_sig": false,
"md5_digest": "de268def11a14b41881d6a436dd91b2b",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 35935,
"upload_time": "2024-09-25T06:56:45",
"upload_time_iso_8601": "2024-09-25T06:56:45.550117Z",
"url": "https://files.pythonhosted.org/packages/f7/44/606bb4e2b943ea918c92e827311439f34c9fc04287cc401ff730a6e6be09/infrable-0.1.40.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-09-25 06:56:45",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "stckme",
"github_project": "infrable",
"github_not_found": true,
"lcname": "infrable"
}
