Saravanan666/pypi-org huggingface dataset:
Package: ansible-pygments
Pygmentslexer and style Ansible snippetsThis project provides aPygmentslexer that is able to handleAnsibleoutput. It may be used anywhere Pygments is integrated.
The lexer is registered globally under the nameansible-output.It also provides aPygmentsstyle for tools needing to highlight
code snippets.The code is licensed under the terms of theBSD 2-Clause license.Using the lexer inSphinxMake sure this library in installed in the same env as yourSphinxautomation viapip install ansible-pygments sphinx. Then, you should
be able to use a lexer by its nameansible-outputin the code blocks
of your RST documents. For example:..code-block::ansible-output[WARNING]: Unable to find '/nosuchfile' in expected paths (use -vvvvv to see paths)ok: [localhost] => {"msg": ""}Using the style inSphinxIt is possible to just setansibleinconf.pyand it will "just
work", provided that this project is installed alongsideSphinxas
shown above.pygments_style='ansible'
Package: ansible-pylibssh
pylibssh: Python bindings to client functionality of libssh specific to Ansible use caseNightlies @ Dumb PyPI @ GitHub PagesWe publish nightlies on tags and pushes to devel.
They are hosted on a GitHub Pages based index generated
bydumb-pypi.The web view is @https://ansible.github.io/pylibssh/.$pipinstall\--extra-index-url=https://ansible.github.io/pylibssh/simple/\--pre\ansible-pylibsshRequirementsYou need Python 3.6+pylibssh requires libssh to be installed in particular:libssh version 0.9.0 and later.To install libssh refer to itsDownloads page.Building the moduleIn the local env, assumes there’s a libssh shared library
on the system, build toolchain is present and env vars
are set properly:$gitclonehttps://github.com/ansible/pylibssh.git$cdpylibssh$pipinstalltox$tox-ebuild-distsmanylinux-compatible wheels:$gitclonehttps://github.com/ansible/pylibssh.git$cdpylibssh$pipinstalltox$tox-ebuild-dists-manylinux1-x86_64# with Docker#orwithPodman$DOCKER_EXECUTABLE=podmantox-ebuild-dists-manylinux1-x86_64#toenableshellscriptdebugmodeuse$tox-ebuild-dists-manylinux1-x86_64---eDEBUG=1LicenseThis library is distributed under the terms of LGPL 2 or higher,
see fileLICENSE.rstin this repository.
Package: ansible-qt-launcher
QT Launcher for ansible - Make your ansible tasks easyA Helper pip package for ansible tasks. This pip package helps you automate your CI/CD pipeline.Assumptions:Assuming python is installed on your system.Ansible is installed on your systemInstallansible-qt-launceron your system using :pip install ansible-qt-launcherfollow this link for more detailshttps://dzone.com/articles/executable-package-pip-install
Package: ansible-repo
ANSIBLE-REPOusage:ansible-repo is a command which allowed ansible to download a git repository and run it as a playbook

Usage:
  ansible-repo <repo> <tag> [-e <env_vars>] [-vvv]
  ansible-repo <repo> <tag> -i <inventory> [-e <env_vars>] [-vvv]

Option:
  -v	verbose
  -i    inventory
  -e    Ansible environment variables
Package: ansible-role-algosec
AlgoSec Ansible Role====================|docs| |travis| |coverage|.. |docs| image:: https://readthedocs.org/projects/algosec-ansible-role/badge/:target: http://algosec-ansible-role.readthedocs.io/en/latest/:alt: Documentation Status.. |coverage| image:: https://img.shields.io/codecov/c/github/algosec/algosec-ansible-role.svg:target: https://codecov.io/gh/algosec/algosec-ansible-role.. |travis| image:: https://travis-ci.com/algosec/algosec-ansible-role.svg?branch=master:target: https://travis-ci.com/algosec/algosec-ansible-roleAnsible role to DevOps-ify network security management, leveraging AlgoSec's business-driven security policy management solutionDocumentation available online at: http://algosec-ansible-role.readthedocs.io/en/latest/Requirements------------* This module is supported and fully tested under ``python2.7`` and ``python3.6``.* All modules of this role require environment::pip install algosec --upgradepip install ansible marshmallow urllib3Installation------------The Ansible role can be installed directly from Ansible Galaxy by running::ansible-galaxy install algosec.algosecIf the ``ansible-galaxy`` command-line tool is not available (usually shipped with Ansible), or you prefer to download the role package directly,navigate to the Ansible Galaxy `role page <https://galaxy.ansible.com/algosec/algosec/>`_ and hit "Download".Alternately, you can directly navigate to our `GitHub repository <https://github.com/algosec/algosec-ansible-role>`_.Usage--------------Once installed, you can start using the modules included in this role in your ansible playbooks.To quickly get up and running a simple example you can follow these steps:1. Download and unzip locally the examples folder by clicking `here <https://minhaskamal.github.io/DownGit/#/home?url=https://github.com/algosec/algosec-ansible-role/tree/master/examples>`_.2. Update authentication credentials in ``vars/algosec-secrets.yml``.3. Update your AlgoSec server IP in ``inventory.ini``.4. Update the arguments of the relevant modules in one of the playbooks (files with the ``yml`` extension).5. Run ``ansible-playbook -i inventory.ini <playbook-filename>.yml``.6. You've made it!Documentation-------------.. image:: https://readthedocs.org/projects/algosec-ansible-role/badge/:target: https://algosec-ansible-role.readthedocs.io/en/latest/:alt: Documentation StatusDocumentation available online at: https://algosec-ansible-role.readthedocs.io/en/latest/How to build doc's locally?^^^^^^^^^^^^^^^^^^^^^^^^^^^Using Docker, running from one folder outside of the project::$ docker run -it -v $PWD/ansible-role-algosec/:/documents/ ivanbojer/spinx-with-rtd$ cd docs$ make htmlUsing Spinx::$ cd docs$ make htmlThen see the ``docs/_build`` folder created for the html files.License-------MIT (see full license `here <http://algosec-ansible-role.readthedocs.io/en/latest/license.html>`_)Author Information------------------AlgoSec Official Websitehttps://www.algosec.com/Development-----------To kickoff local development, just use `pipenv`::pipenv installAnd to use the newly installed virtual environment just run::pipenv shell
Package: ansible_role_apply
Apply a single Ansible role to host(s) easilyExample usage$ansible-role-apply--helpUsage:ansible-role-apply[OPTIONS]ROLEHOSTSOptions:-s,--sudo/--no-sudo--show-playbook/--no-show-playbook--helpShowthismessageandexit.$ansible-role-applydockervagrant--sudo...PLAY[vagrant]****************************************************************GATHERINGFACTS***************************************************************ok:[vagrant]...PLAYRECAP********************************************************************vagrant:ok=16changed=1unreachable=0failed=0$ansible-role-applydockervagrant--sudo--show-playbook-------------------------------------------------------------------------------#!/usr/bin/env ansible-playbook----hosts:-vagrantroles:-dockersudo:True-------------------------------------------------------------------------------|--->pluginactivated:/Users/marca/dev/surveymonkey/smstack/smstack/ansible/plugins/no_hosts_matched_fail.pyc|--->pluginactivated:/Users/marca/dev/surveymonkey/smstack/smstack/ansible/plugins/sm_app_role.pyc|--->pluginactivated:/Users/marca/dev/surveymonkey/smstack/smstack/ansible/plugins/teamcity_messages.pycPLAY[vagrant]****************************************************************...PLAYRECAP********************************************************************vagrant:ok=16changed=1unreachable=0failed=0
Package: ansible-role-atos-hsm
A role to manage ATOS Hardware Security Module (HSM) client software.Role VariablesNameDefault ValueDescriptionatos_client_working_dir/tmp/atos_client_installWorking directory in the target host.atos_client_iso_nameNoneFilename for the ATOS Client Software ISO.atos_client_iso_locationNoneFull URL where a copy of ATOS Client ISO can be downloaded.atos_client_cert_locationNoneFull URL where the client certificate can be downloaded.atos_client_key_locationNoneFull URL where the client key can be downloaded.atos_hsmsNoneList of one or more HSM devices.Requirementsansible >= 2.4UsageYou’ll need to set up a temporary HTTP server somewhere that is accessible
to the node where this role will be applied.  The HTTP server should serve
the following:ATOS Client Software ISO file.HSM Server Certificate file(s).HSM Client Certificate file.HSM Client Key file associated with the Client Certificate.Due to the sensitive nature of the Certificate and Key files, you should
use TLS encryption and username and passwords to access the HTTP server.Use the hostname and user/password for your HTTP server for the full URL values
that need to be set for this role.  Seevars.yaml.example.
Package: ansible-role-chrony
A role to manage chronyRole VariablesVariables used for chronyNameDefault ValueDescriptionchrony_debugFalseEnable debug option in chronychrony_role_actionallAnsible action when including the role. Should be one of: [all|install|config|upgrade|online]chrony_package_namechronychrony system package namechrony_service_namechronydchrony system service namechrony_manage_serviceTrueFlag used to specific if the ansible role should manage the servicechrony_manage_packageTrueFlag used to specific if the ansible role should manage the packagechrony_service_statestartedDefault service state to configure (started|stopped)chrony_config_file_location/etc/chrony.confChrony configuration file location.chrony_driftfile_path/var/lib/chrony/driftChrony drift file locationchrony_logdir_path/var/log/chronyChrony log directory locationchrony_ntp_servers[]List of NTP servers. This can be a list of hashes for advanced configuration.
If using the hash format, aserver_nameandserver_settingskey should be populated with
the appropriate data. If this is a list of hostnames, thechrony_global_server_settingswill be appended to the configuration.chrony_global_server_settings<none>Default setting to apply to the servers configurationchrony_ntp_pools[]List of NTP pools. This can be a list of hashes for advanced configuration.
If using the hash format, apool_nameandpool_settingskey should be populated with
the appropriate data. If this is a list of hostnames, thechrony_global_pool_settingswill be appended to the configuration.chrony_global_pool_settings<none>Default setting to apply to the pools configurationchrony_ntp_peers[]List of NTP peers. This can be a list of hashes for advanced configuration.
If using the hash format, apeer_nameandpeer_settingskey should be populated with
the appropriate data. If this is a list of hostnames, thechrony_global_peer_settingswill be appended to the configuration.chrony_global_peer_settings<none>Default setting to apply to the peers configurationchrony_bind_addresses[‘127.0.0.1’, ‘::1’]List of addresses to bind to to listen for command packetschrony_acl_rules[]List of specific allow/deny commands for the configuration filechrony_rtc_settings[‘rtcsync’]List of specific real time lock settingschrony_makestep1.0 3The chrony makestep configurationchrony_extra_options[]A list of extra option strings that is added to the end of the configuration file. This list is joined with new lines.Requirementsansible >= 2.4python >= 2.6DependenciesNoneExample Playbooks- hosts: localhost
  become: true
  roles:
    - chronyLicenseApache 2.0
Package: ansible-role-container-registry
A role to deploy a container registry and provide methods to login to it.
For now, the role only support Docker Registry v2.
The login currently doesn’t work with hub.docker.com.Role VariablesVariables used for container registryNameDefault ValueDescriptioncontainer_registry_debugfalseEnable debug option in Dockercontainer_registry_deploy_dockertrueWhether or not to deploy Dockercontainer_registry_deploy_docker_distributiontrueWhether or not to deploy Docker Distributioncontainer_registry_deployment_usercentosUser which needs to manage containerscontainer_registry_docker_options–log-driver=journald –signature-verification=false –iptables=false –live-restoreOptions given to Docker configurationcontainer_registry_docker_disable_iptablesfalseAdds –iptables=false to /etc/sysconfig/docker-network configcontainer_registry_insecure_registries[]Array of insecure registriescontainer_registry_network_options[undefined]Docker networking optionscontainer_registry_hostlocalhostDocker registry hostcontainer_registry_port8787Docker registry portcontainer_registry_mirror[undefined]Docker registry mirrorcontainer_registry_storage_options-s overlay2Docker storage optionscontainer_registry_selinuxfalseWhether or not SElinux is enabled for containerscontainer_registry_additional_sockets[undefined]Additional sockets for containerscontainer_registry_skip_reconfigurationfalseDo not perform container registry reconfiguration if it’s already configuredcontainer_registry_logins[]A dictionary containing registries and a username and a password associated with the registry.
Example: {‘docker.io’: {‘myusername’: ‘mypassword’}, ‘registry.example.com:8787’: {‘otheruser’: ‘otherpass’}}Requirementsansible >= 2.4python >= 2.6DependenciesNoneExample PlaybooksModify ImageThe following playbook will deploy a Docker registry:- hosts: localhost
  become: true
  roles:
    - container-registryLicenseApache 2.0Running local testingLocal testing of this role can be done in a number of ways.Mimic ZuulSometimes its nessisary to setup a test that will mimic what the OpenStack gate
will do (Zuul). To run tests that minic the gate,python-virtualenvgit,gcc, andansibleare required.$sudoyuminstallpython-virtualenvgitgccOnce the packages are installed, create a python virtual environment.$python-mvirtualenv--system-site-packages~/test-python$~/test-python/bin/pipinstallpipsetuptools--upgradeNow install the latest Ansible$~/test-python/bin/pipinstallansibleWith Ansible installed, activate the virtual environment and run therun-local.ymltest playbook.$source~/test-python/bin/activate(test-python)$ansible-playbook-i'localhost,'\-e"tripleo_src=$(realpath--relative-to="${HOME}""$(pwd)")"\-e"ansible_user=${USER}"\-e"ansible_user_dir=${HOME}"\-e"ansible_connection=local"\zuul.d/playbooks/run-local.ymlRunning Molecule directlyIt is also possible to test this role using molecule directly. When running
tests directly it is assumed all of the dependencies are setup and ready to
run on the local workstation. When$moleculetest--all
Package: ansible-role-lunasa-hsm
A role to manage Thales Luna Network Hardware Security Module (HSM) clients.Role VariablesThis ansible role automates the configuration of a new client for the
Thales Luna Network HSM.NameDefault ValueDescriptionlunasa_client_working_dir/tmp/lunasa_client_installWorking directory in the target host.lunasa_client_tarball_nameNoneFilename for the Lunasa client software tarball.lunasa_client_tarball_locationNoneFull URL where a copy of the client software tarball can be downloaded.lunasa_client_installer_pathNonePath to the instal.sh script inside the tarball.lunasa_client_pinNoneThe HSM Partition Password (PKCS#11 PIN) to be used by the client.lunasa_client_ipNone(Optional) When set, this role will use the given IP to register
the client instead of the client’s fqdn.lunasa_client_rotate_certFalseWhen set to True, the role will generate a new client certificate
to replace the previous one.lunasa_hsmsNoneList of dictionaries, each of which describes a single HSMsee vars.sample.yamlfor details.  When more than one HSM is
listed here, the client will be configured in HA mode.Requirementsansible >= 2.4
Package: ansible-role-manager
Project page and docs:http://mirskytech.github.io/ansible-role-managerDevelopment:https://github.com/mirskytech/ansible-role-managerFeature & issue tracking:https://github.com/mirskytech/ansible-role-manager/issuesPackage Index:https://pypi.python.org/pypi/ansible-role-managerDescriptionProvides the following utilities:initCreates the Ansible recommended folder structure and initial core files for playbooks, roles and modules.installInstalls Ansible roles from Ansible Galaxy or located in any version control repository (git, mercurial and svn).uninstallRemove dependencies from the playbook’s libraryfreezeCreate list of installed dependencies for a playbookseearm helpfor all availble commands.Installation of Ansible Role Manager (ARM)Standard installation:>> pip install ansible-role-manageror installation for development:>> pip install -e git+https://github.com/mirskytech/ansible-role-manager.git#egg=role-manageror manual installation:>> git clone https://github.com/mirskytech/ansible-role-manager.git
>> python setup.py installGet StartedCreate a well-structured playbooks (directory structure, initial files):>> arm init -p MyNewPlaybookInstall a role from Ansible Galaxy:>> arm install github_owner.github_repoInstall a role from an arbitrary git repository and name it locally asmyrolename:>> arm install git+ssh://github.com/github_owner/github_repo.gitor install with changing the locally installed name tomyrolename:>> arm install git+ssh://github.com/github_owner/github_repo.git#alias=myrolenameDependenciesmercurialgitpythonansiblerequestsgitpython (0.3.2.RC1)coloramahgapiReferencesAnsiblehttp://docs.ansible.com/Ansible Galaxyhttps://galaxy.ansible.com/exploreRelease Notes & Roadmaphttp://mirskytech.github.io/ansible-role-manager/releasenotes.html
Package: ansible-roles-ctl
Ansible roles managementThe goal of this tool is to manage installation and upgrade of Ansible
roles and collections using git tags and branches.This tool uses therequirements.ymlconfiguration file used by Ansible
Galaxy. The syntax is unchanged and the ansible-galaxy tool can be used
by people not involved in playbooks development. Version 1 of the requirements
file with only a list of roles is still supported, but if you need collections
then you need to convert it to version 2 (containing a list of 'roles' and a
list of 'collections').Support for collections is limited to installing a full repo with all included
collections. This means all included collections (if many) will be enabled and
you cannot select to enable just some of them. The name of the collection must
contain the namespace to be installed in the proper path (as defined in Ansible
documentation). For example:roles:
…
collections:
  - name: kubernetes.core
    type: git
    source: https://github.com/ansible-collections/kubernetes.core.git
    version: stable-2.2will install it at<collections_path>/ansible_collections/kubernetes/core/withcollections_pathdefined in youransible.cfgor using Ansible default.This tool assumes arole/collection versionfollowssemantic versioningand is labelled with a git tag of the formvX.YorvX.Y.Z(examples: v1.0 or v2.3.1). In fact thevis optional but recommended for clarity.Roles managed manually, bare, or in a bad shape are ignored (with proper
warning).InstallationYou can install it using PyPI:pip install ansible-roles-ctlOr you can run it in-place since it has very few dependencies (you only
need the ansible-roles-ctl script, version.py is only used in the build
process).You need the following dependencies:Ansible (probably starting from 2.7)GitPython(package 'python3-git' on Debian systems, or using pip)argcomplete>= 1.9.2 (package 'python3-argcomplete' on Debian systems, or using pip)CompletionCommand completion is done usingargcomplete.
It needs to be enabled first to work. The easiest way is to use theactivate-global-python-argcomplete3script as root. Other methods are
described on theargcompletewebsite.UsageSyntax is as follow:ansible-roles-ctl [global options] [subcommand] [subcommand options]You can use -h/--help option to list all available options at command
and subcommand level, as well as all available subcommands.Follows documentation about the various subcommands.Statusansible-roles-ctl statusThis subcommand display a status report about all required roles/collections.You can limit output to a selection of roles/collections:ansible-roles-ctl status mailman3 httpdThe -c/--changelog option displays changelog entries if available.Installansible-roles-ctl installThis subcommand install all roles/collections listed in the requirements.You can limit this action to a selection of roles/collections:ansible-roles-ctl install bind9 postfixUpdateansible-roles-ctl updateThis subcommand update all roles/collections listed in the requirements to the
latest version.You can limit this action to a selection of roles/collections:ansible-roles-ctl update bind9 postfix
Package: ansible-roles-graph
# ansible-roles-graphGenerate a graph of Ansible role dependencies.## Installpip install ansible-roles-graphAssuming you already installed [graphviz](http://www.graphviz.org/)
with [python bindings](http://www.graphviz.org/content/python-graphviz).## UsageQuite simply:ansible-roles-graphWill look for roles in the./roles/directory, and generate an./ansible-roles.pngfile.The command also accepts multiple role directories and various options:ansible-roles-graph -o schema.png -f png roles/ ../other/rolesSeeansible-roles-graph –helpfor more info.## Output![PNG example](./example.png)## License[GNU GPLv3 or later](https://www.gnu.org/licenses/gpl.html)
Package: ansible-role-thales-hsm
This is a role to manage the client software for Entrust nShield Connect
Hardware Security Modules (HSMs).This repo uses the “Thales” name for historical reasons:At the time when this repository was created nShield HSMs were owned by Thales.
Since then, the nShield line of HSMs have gone through some ownership changes,
including nCipher for some time, and currently Entrust.If you are looking for the ansible role to manage client software for
Thales Luna Network HSMs you can find it here:https://opendev.org/openstack/ansible-role-lunasa-hsmRole VariablesNameDefault ValueDescriptionthales_install_clientfalseWhether the role should install the client software on the target host.thales_configure_rfsfalseWhether the role should execute the RFS configuration tasks.thales_client_working_dir/tmp/thales_client_installWorking directory in the target host.thales_client_gid42481Group ID for the thales group.thales_client_uid42481User ID for the thales user.thales_client_tarball_nameNoneFilename for the Thales client software tarball.thales_client_tarball_locationNoneFull URL where a copy of the client software tarball can be downloaded.thales_client_pathlinux/libc6_11/amd64/nfastPath to the client software directory inside the tarballthales_km_data_tarball_nameNoneFilename for the KM Data tarballthales_km_data_locationNoneFull URL where a copy of the KM Data tarball can be downloaded.thales_rfs_ip_addressNoneIPv4 address for the Thales RFS host.thales_client_ipsNoneWhitespace separated list of IP addresses to be added to RFS config.thales_bootstrap_client_ipNoneBootstrap client IP address.  This IP will be allowed to update RFS
server.nshield_hsmsNoneList of one or more HSM devicesRequirementsansible >= 2.4