Saravanan666/pypi-org huggingface dataset:
Package: ansible-bundle
# ansible-bundleSmall tool for automatic download roles and libs a-la-Gemfile# PreambleAs many roles have changed their configurations among time, anyone would use aspecific version of a role (for instance, a commit, or a branch, or a tag).Moreover, a complex playbook could need different versions from the same role.This app will download roles (bundles, from now on) from theirrepositories before launching a playbook. _That means that a role should be inits own repository_.# Prerequisites- Ansible. Any version.- Git >= 1.8.5- Python 2 >= 2.6# Installation## The easy way: pip`sudo pip install ansible-bundle`## The not-that-easy way: from code- Download [latest release](../../archive/master.zip)- Run `sudo python setup.py`# Syntax`ansible-bundle FILEYAML [ansible-playbook-options] [ansible-bundle-options]`ansible-bundle, along the ansible-playbook parameters, has also these:- `--bundle-clean-roles` Will clean roles and library directories before download (*)- `--bundle-dry` Shows what will be run (as it won't download anything,also won't search for dependencies)- `--bundle-deps-only` Don't run the playbook, just satisfy dependencies.- `--bundle-disable-color` Useful for non-interactive consoles- `--bundle-workers` concurrent connections when downloading/updating roles. Default: 1- `--bundle-safe-update` Don't clean existing roles. (*)(*) If both `bundle-clean-roles` and `bundle-safe-update` are set, `bundle-clean-roles` will take effect.# Configurationansible-bundle expects to find a `[bundle]` section into ansible.cfg, which maycontain some of the command lines parameters:- workers- verbosity- safeAnd the following extra options:- `url`: URL where the roles are located. For example, if role `apache` is in`github.com/foo/roles/apache`, the `url` should be set to `github.com/foo/roles`.Default is 'https://github.com'## bundle.cfg example[bundle]url='git@github.com:devopsysadmin/ansible-roles'workers=5verbosity=1# Example of useGiven the following playbook (site.yml):- include: site-common.ymltags:- common- hosts: allroles:- postgresql@1.0- { role: apache, version: '2.4' }Running `ansible-bundle site.yml` will search roles into the `site-common.yml` file andadd to download queue, which already includes postgresql 1.0 and apache master.Please note that each role is intended to be in its own repository, not in a folder.# Changelog## v 0.6- Syntax role/version changes to role@version. This simplifies the configuration inansible.cfg and allows branches names such as feature/something in role version.If a versioned role with the previous syntax is found, will complain with adeprecation warning. The previous syntax will be obsoleted in v 0.7.# AuthorDavid Pedersen (david.3pwood AT gmail DOT com)# LicenseGNU Public License v2 (GPLv2)
Package: ansible-cached-lookup
ansible-cached-lookupAn Ansible lookup plugin that caches the results of any other lookup, most
useful in group/host vars.By default, Ansible evaluates any lookups in a group/host var whenever the var
is accessed. For example, given a group/host var:content:"{{lookup('pipe','a-very-slow-command'}}"any tasks that accesscontent(e.g. in a template) will re-evaluate the
lookup, which adds up very quickly. Seeansible/ansible#9263.InstallationPick a name that you want to use to call this plugin in Ansible playbooks.
This documentation assumes you're using the namecached.pip install ansible-cached-lookupCreate alookup_pluginsdirectory in the directory in which you run Ansible.By default, Ansible will look for lookup plugins in anlookup_pluginsfolder
adjacent to the running playbook. For more information on this, or to change
the location where Ansible looks for lookup plugins, see theAnsible
docs.Create a file calledcached.py(or whatever name you picked) in thelookup_pluginsdirectory, with one line:fromansible_cached_lookupimportLookupModuleContributingTo run the tests, runtox.To format code to passtox -e lint, runtox -e format.
Package: ansible-collections.python.dist.boo
ansible-collections.python.dist.boo: an Ansible Collection containing a boo moduleThis is a demo of anAnsible Collectionpython.distpackaged
as aPython distribution package. It contains only oneAnsible
modulecalledboo. Given that this dist and Ansible are
installed into the same (virtual)env, it’s accessible from Ansible byFQDNpython.dist.boo. Here’s how you can call it adhoc-style:$ PYTHONPATH=`pwd` ansible -m python.dist.boo -a name=Bob localhost
[WARNING]: No inventory was parsed, only implicit localhost is available
localhost | SUCCESS => {
    "changed": false,
    "greeting": "Hello, Bob!",
    "msg": "Greeting Bob completed."
}Alternatively, install it, instead of mangling withPYTHONPATH:$ pip install ansible-collections.python.dist.boo
$ ansible -m python.dist.boo -a name=Bob localhost
[WARNING]: No inventory was parsed, only implicit localhost is available
localhost | SUCCESS => {
    "changed": false,
    "greeting": "Hello, Bob!",
    "msg": "Greeting Bob completed."
}PurposeAt the moment of publishing this project, this demo only works with
the code supplied byAnsible PR #67093. One can test it by
installing Ansible from that PR-branch:$ pip install git+https://github.com/sivel/ansible@acd-content-dirPublishing to PyPIThis project implements automatic building and publishing of a Python
distribution package to PyPI for tagged commits and to TestPyPI for
every push tomaster. All the heavy lifting is done by the
combination of GitHub Actions CI/CD workflows,pep517CLI tool andsetuptools-scm.The published dists are then installable by:$ pip install ansible-collections.python.dist.boo  # for PyPIand$ pip install ansible-collections.python.dist.boo \
      -i https://test.pypi.org/simple/ --pre  # for TestPyPIIf you’re learning by example, take a look at the following files:pyproject.tomlsetup.cfg.github/workflows/publish-to-test-pypi.ymlBesides, you can follow aPyPA guide about publishing packages via
GitHub Actionsthat will walk you through the process.PrerequisitesPython 3.7+LicenseThe source code and the documentation in this project are released under
theGPL v3 license.
Package: ansible-compose
Deploying a docker-compose.ymlFirst, configure the dsn variable to have the user/host and path to store the
compose files in. If not set, localhost in current working directory will be
used:export dsn=user@host:22/absolute/target/pathThen, run ansible-compose apply -f as you would with k8s:ansible-compose apply -f ./docker-compose-example.yml -f ./examples/nginx.ymlOr, deploy from a url, just like kubectl apply would let you:ansible-compose apply -f https://raw.git.../docker-compose.ymlRunning commands on the compose of a targetProvide ssh configuration and target dir as first argument, then the
docker-compose command:export dsn=user@host:22/absolute/target/path
ansible-compose stop
ansible-compose start
ansible-compose logs
ansible-compose helpTransforms for docker-compose.yml on the CLITransforms apply on the docker-compose.yml as if it was a template we are going
to render using environment variables.Suppose that you start with such a docker-compose.yml:version:'3.4'services:web:build:.environment:base:herewrong:todropFirst, all build lines will be dropped. You will have to
specify images with env vars ie.:web_image=abc  # sets services[web][image]=abcIf you wanted to drop the environment line use the drop
prefix:drop_web_environment=  # dels services[web][environment]You can also override deeper in the YAML tree:web_environment_SECRET_TOKEN=yoursecretEven for drop:drop_web_environment_VERSION=Or even drop a whole service:drop_web=You can however require all variables to have a particular prefix, ie:dev_drop_mail=              # to prevent the mail service on dev branches
ansible_compose_prefix=dev  # to enable only variables starting with dev_Don’t forget ansible-compose will also forward extraneous arguments to the
ansible-playbook call beneath.Automatic creation of volume dirsIt will try to automatically create the volume bind dirs for you. To set the
uid and/or guid, set them as env vars, either in the compose.yml:environment:
  uid: 1001
  gid: 100Or with an env var:web_environment_uid=1001InstallationLocal:pip install --user ansible-compose
export PATH="$HOME/.local/bin:$PATH"
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrcThe current configuration in CI for image yourlabs/ansible-compose is:ANSIBLE_HOST_KEY_CHECKING=falseSSH_PRIVATE_KEY=our passwordless private key generated with ssh-keygen -t ed25519 and default optionsSSH_INSECURE=true not checking any host key today !Example gitlab ci jobdeploy:stage:deployimage:yourlabs/ansible-composevariables:-dsn=deploy@example.com/home/stagingscript:-ansible-compose apply -f ./docker-compose.yml
Package: ansible-config-template
Team and repository tagsOpenStack-Ansible config_templateThis module is an ansible plugin that extends regular template functionality
with the ability to override items in config, in transit, through the use
of a simple dictionary without having to write out various temp files on target
machines.WARNINGInstallation from PyPI or as a Python module is deprecated and will be removed
in future releases.
Please, use ansible-galaxy to install the collection.More infromation about the projectDocumentation for the project can be found at:https://docs.openstack.org/ansible-config_template/latest/Release notes for the project can be found at:https://docs.openstack.org/releasenotes/ansible-config_template/The project source code repository is located at:https://opendev.org/openstack/ansible-config_template/The project home is at:https://launchpad.net/openstack-ansibleThe project bug tracker is located at:https://bugs.launchpad.net/openstack-ansible
Package: ansibleconnect
Ansibleconnect - connect to all hosts from the inventory with one commandAnsible VersionCI Status2.52.62.72.82.9SSH into all hosts in your inventory with one command.Ansibleconnect creates a bash script based on your ansible inventory.
That script will create a new tmux window or session and create a separate pane
for each one of your 'sshable' inventory hosts. Inside of each of the
panes an ssh connection to the pane's host will be established.Setup example (on Ubuntu):sudo apt install tmux
sudo apt install sshpass
pip install ansibleconnectUsage examples:Connect to all hosts in inventory:source <(ansibleconnect -i inventory.yml)Connect to all hosts from group1 and group2:source <(ansibleconnect -i inventory.yml -g 'group1:group2')Connect to all hosts from group1 except for hosts that are also in group2:source <(ansibleconnect -i inventory.yml -g 'group1:!group2')Connect to all hosts from inventory except for hosts in group1:source <(ansibleconnect -i inventory.yml -g '!group1')Connect to all hosts that have AWS provider:source <(ansibleconnect -i inventory.yml -vars provider:aws)>NOTE:In case you don't use bash. You can also useevalcommand, for example:eval "$(ansibleconnect -i inventories/inventory.yml)"Possible flags-i,--inventory- Path to ansible inventory-g,--groups- Inventory groups of hosts to connect to (multiple groups should be concentrated with:.!in front of group name means that ansibleconnect should not connect to hosts form this group). Example:-g computes:!storage--hosts- List of hostnames to connect to. Example:--hosts hostA,hostB-vars,--variables- Variables that host should have defined in inventory to connect to it. Accepted format:key:valuein case where host should have variable with specific value orkeyin case where host should have defined variable no matter what value. Example:-v type:dev,team:ui-novars,--no-variables- Variables that host should not have defined in inventory to connect to it. Accepted format:key:valuein case where host should not have variable with specific value orkeyin case where host should not have defined variable no matter what value.Example:-novars type:prod,team:salesConfigurationAnsibleconnect looks for theansible.cfgfile in the same locations as ansible.Authenticationssh-agentFor authentication one can use ssh keys.ansibleconnectwill scan the inventory file for connection options (ansible_ssh_common_args,ansible_ssh_user,ansible_host,ansible_private_key_file, etc.). Ssh keys can be passed via them. Otherwise, one can use thessh-agenttool. Environment args (SSH_AGENT_PIDandSSH_AUTH_SOCK) will be passed to each one of the tmux shells.ssh-agent setup exampleeval $(ssh-agent)
ssh-add ~/.ssh/my_private_key.pemsshpassIfansible_ssh_passvariable is used in the inventory, one should install thesshpassand make it discoverable viaPATH. Please note that when using the sshpass, password will passed in plaintext and it will be saved in each of the tmux shells' history.
Package: ansible-core
AnsibleAnsible is a radically simple IT automation system. It handles
configuration management, application deployment, cloud provisioning,
ad-hoc task execution, network automation, and multi-node orchestration. Ansible makes complex
changes like zero-downtime rolling updates with load balancers easy. More information on the Ansiblewebsite.Design PrinciplesHave an extremely simple setup process with a minimal learning curve.Manage machines quickly and in parallel.Avoid custom-agents and additional open ports, be agentless by
leveraging the existing SSH daemon.Describe infrastructure in a language that is both machine and human
friendly.Focus on security and easy auditability/review/rewriting of content.Manage new remote machines instantly, without bootstrapping any
software.Allow module development in any dynamic language, not just Python.Be usable as non-root.Be the easiest IT automation system to use, ever.Use AnsibleYou can install a released version of Ansible withpipor a package manager. See ourinstallation guidefor details on installing Ansible
on a variety of platforms.Power users and developers can run thedevelbranch, which has the latest
features and fixes, directly. Although it is reasonably stable, you are more likely to encounter
breaking changes when running thedevelbranch. We recommend getting involved
in the Ansible community if you want to run thedevelbranch.Get InvolvedReadCommunity Informationfor all
kinds of ways to contribute to and interact with the project,
including mailing list information and how to submit bug reports and
code to Ansible.Join aWorking Group,
an organized community devoted to a specific technology domain or platform.Submit a proposed code update through a pull request to thedevelbranch.Talk to us before making larger changes
to avoid duplicate efforts. This not only helps everyone
know what is going on, but it also helps save time and effort if we decide
some changes are needed.For a list of email lists, IRC channels and Working Groups, see theCommunication pageCoding GuidelinesWe document our Coding Guidelines in theDeveloper Guide. We particularly suggest you review:Contributing your module to AnsibleConventions, tips, and pitfallsBranch InfoThedevelbranch corresponds to the release actively under development.Thestable-2.Xbranches correspond to stable releases.Create a branch based ondeveland set up adev environmentif you want to open a PR.See theAnsible release and maintenancepage for information about active branches.RoadmapBased on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.7, 2.8).
TheAnsible Roadmap pagedetails what is planned and how to influence the roadmap.AuthorsAnsible was created byMichael DeHaanand has contributions from over 5000 users (and growing). Thanks everyone!Ansibleis sponsored byRed Hat, Inc.LicenseGNU General Public License v3.0 or laterSeeCOPYINGto see the full text.
Package: ansible-coverage-callback
# ansible-coverage-callback[![Latest version](https://img.shields.io/pypi/v/ansible-coverage-callback.svg)](https://pypi.python.org/pypi/ansible-coverage-callback/)[![License](https://img.shields.io/badge/license-MIT-brightgreen.svg)](https://opensource.org/licenses/MIT)Coverage Tool for Ansible.## Requirements* Ansible >=2.4## InstallationInstall this Ansible plugin with:```$ pip install ansible-coverage-callback```Be sure to whitelist the plugin in your `ansible.cfg`:```[defaults]callback_whitelist = coverage```## Skip coverage tagYou may skip task or tasks from coverage report by adding `skip_coverage` tag:```---- name: Test handlercommand: whoamiwhen:- test_var == Falsetags:- skip_coverage```## Acknowledged issues* Imported handlers has no tags, so they can't be skipped* There is some magic hacks for skipping Molecule's system playbooks* Tasks from non imported files are not counted
Package: ansible-creator
ansible-creatorA CLI tool for scaffolding all your Ansible Content.Installation$pipinstallansible-creator$ansible-creator--help
usage:ansible-creator[-h][--version]{init}...

TooltoscaffoldAnsibleContent.Getstartedbylookingatthehelptext.

optionalarguments:-h,--helpshowthishelpmessageandexit--versionPrintansible-creatorversionandexit.

Commands:{init}Thesubcommandtoinvoke.initInitializeanAnsibleCollection.UsageFull documentation on how to use this, along with it's integration with VS Code Ansible Extension can be found inhttps://ansible.readthedocs.io/projects/creator/.Upcoming featuresScaffold Ansible plugins of your choice with thecreateaction.
Switch to thecreatebranch and try it out!Licensingansible-creator is released under the Apache License version 2.See theLICENSEfile for more details.
Package: ansible-cry
CRYEncrypt and decrypt ansible-vault string/file perfect external toolsCRY me a river of encrypted data. Cry cry Cry.

Utilisation:
    cry [OPTIONS] [SUB_COMMAND [OPTIONS]] 

Meta-options:
    -h, --help                        Print this message
    --help-all                        Prints help messages of all sub-commands and quits
    -v, --version                     Show version

Options:
    --config VALEUR:ExistingFile      Filename with the vault password.; default: $HOME/.vault.pass
    -d, --decrypt                     Encrypt by default, add -d to decrypt
    --show-params                     Show parameters given to cry and exit.

Sub-commands:
    file                              see 'cry file --help' for infos
    string                            see 'cry string --help' for infosUtilisation:
    cry file [OPTIONS] files...

Hidden-switches:
    -h, --help              Print this message
    --help-all              Prints help messages of all sub-commands and quits
    -v, --version           Show version

Options:
    -c, --show-context      Show the context around the string to decodeUtilisation:
    cry string [OPTIONS] strings...

Hidden-switches:
    -h, --help         Print this message
    --help-all         Prints help messages of all sub-commands and quits
    -v, --version      Show version

Options:
    -s, --stdin        Use stdin as source
Package: ansible-deployer
ansible-deployerHowever ansible is a great tool for IT infrastructure automation in certain cases it's hard to use
it for the complete deployment, because of that tools like ansible-tower/AWX try to wrap it's
activity making further assumptions on the way ansible code is stored (versioning repository), the
way it's executed - certain combinations of inventory/playbook/tag options used to achieve specific
goals. Having it in mind ansible-deployer may be treated as yet another ansible-playbook wrapper, but
focused on comprehensive command line intrface and easy YAML based configuration.Some main fatures areThe results of whole excution are logged and saved together with the ansible code state for
potential review in the future.Only one active ansible-deployer per ansible inventory is allowed, attempt to execute ansible-deployer
on already locked infrastructure will be rejected.Working directory is setup per every execution of ansible-deployer separately to store the code
state used. This is done by site configurable hook.It's possible to lock/unlock inventory (defined as --infra --stage pairs) for manual manipulation,
stopping ansible-deployer from being used.Configuration filestasks.yaml- Configuration of tasks (sets of playbooks to be executed)infra.yaml- Configuration of infrastructures and stages of those mapping to ansible inventoryExamplesansible-deployer run --task updateUsers --infra webServers --stage prod
Package: ansible-dev-tools
Ansible Development Tools (ADT)Theansible-dev-toolspython package provides an easy way to install and discover the best tools available to create and test ansible content.The curated list of tools installed as part of the Ansible automation developer tools package includes:ansible-core: Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems.ansible-builder: Ansible Builder is a tool that automates the process of building execution environments using the schemas and tooling defined in various Ansible Collections and by the user.ansible-creator: The fastest way to generate all your ansible content!ansible-lint: Checks playbooks for practices and behavior that could potentially be improved.ansible-navigatorA text-based user interface (TUI) for Ansible.ansible-sign: Utility for signing and verifying Ansible project directory contents.molecule: Molecule aids in the development and testing of Ansible content: collections, playbooks and rolespytest-ansible: A pytest plugin that enables the use of ansible in tests, enables the use of pytest as a collection unit test runner, and exposes molecule scenarios using a pytest fixture.tox-ansible: The tox-ansible plugin dynamically creates a full matrix of python interpreter and ansible-core version environments for running integration, sanity, and unit for an ansible collection both locally and in a Github action. tox virtual environments are leveraged for collection building, collection installation, dependency installation, and testing.ansible-dev-environment: A pip-like install for Ansible collections.Installationpython -m pip install ansible-dev-toolsUsageIn addition to installing each of the above tools,ansible-dev-toolsprovides an easy way to show the versions of the content creation tools that make up the current development environment.$ adt --version
ansible-builder                          3.0.0
ansible-core                             2.16.3
ansible-creator                          24.2.0
ansible-dev-environment                  24.1.0
ansible-dev-tools                        0.2.0a0
ansible-lint                             24.2.0
ansible-navigator                        24.2.0
ansible-sign                             0.1.1
molecule                                 24.2.0
pytest-ansible                           24.1.2
tox-ansible                              24.2.0DocumentationFor more information, please visit ourdocumentationpage.
Package: ansible-discover
ansible-discoveransible-discoveris a command line tool to list dependencies and
dependants ofAnsibleroles and playbooks, respectively.One of its prime uses is in a CI tool like Jenkins. Once a change on,
say a role, is committed, useansible-discoverto gather the dependant
roles and playbooks. From this list, the respective CI jobs for playbook
and role validations may then be triggered.Installationpip install ansible-discoverUsageOne use case (like outlined above) is to determine all roles (directly
or indirectly) depending on a given set of roles:ansible-discover roles predecessors PATHSwherePATHSis a space-delimited list of paths to roles (e.g.,roles/my_sample_role).In addition to predecessors (i.e., dependants) for roles, you can also
discoversuccessors (i.e., dependencies) of roles:ansible-discoverroles successors;predecessors for playbooks:ansible-discoverplaybooks predecessors; andsuccessors of playbooks:ansible-discoverplaybooks successors.Related toolsansigenomeansible-roles-graphansible-reviewLicenseDistributed under the XYZ license. SeeLICENSE.txtfor more
information.ContributingFork it!Create your feature branch:git checkout-bmy-new-featureCommit your changes:git commit-am'Add some feature'Push to the branch:git push originmy-new-featureSubmit a pull request :)