ansigenome | gather information and manage your Ansible roles

by nickjj Python Version: 0.6.0 License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | ansigenome Summary

ansigenome is a Python library typically used in Devops, Ansible applications. ansigenome has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. You can install using 'pip install ansigenome' or download it from GitHub, PyPI.

A tool to help you gather information and manage your Ansible roles.

Support

Quality

Security

License

Reuse

Support

ansigenome has a low active ecosystem.

It has 419 star(s) with 53 fork(s). There are 17 watchers for this library.

It had no major release in the last 12 months.

There are 20 open issues and 15 have been closed. On average issues are closed in 62 days. There are 9 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ansigenome is 0.6.0

Quality

ansigenome has 0 bugs and 66 code smells.

Security

ansigenome has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ansigenome code analysis shows 0 unresolved vulnerabilities.

There are 2 security hotspots that need review.

License

ansigenome is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

ansigenome releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

ansigenome saves you 777 person hours of effort in developing the same functionality from scratch.

It has 1789 lines of code, 118 functions and 19 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed ansigenome and discovered the below as its top functions. This is intended to give you an instant insight into ansigenome implemented functionality, and help decide if they suit your requirements.

Scan the roles
Create or augment meta file
Add the main keys to the main key
Make sure meta_dict is consistent
Execute the shell command
Return a dictionary of role names
Run a shell command
Exit if there are no roles
Export the roles
Check if the stream has colors
Read a file into a list
Get the version from a file
Write config to a file
Convert yaml into a nice yaml string

Get all kandi verified functions for this library.

ansigenome Key Features

No Key Features are available at this moment for ansigenome.

ansigenome Examples and Code Snippets

No Code Snippets are available at this moment for ansigenome.

Community Discussions

Trending Discussions on ansigenome

How do I debug Ansible includes and dependencies?

QUESTION

How do I debug Ansible includes and dependencies?

Asked 2017-Aug-30 at 19:15

I've joined a project which has a large number of playbooks and roles, and which makes heavy use of include (often in a nested fashion) in order to include playbooks/roles within existing playbooks/roles. (Whether this is good or bad practice should be considered out of scope of this question, because it's not something I can immediately change. Note also that include_role is not used because these playbooks were written well before 2.2 was out, and are still in the process of being updated.)

Normally when running ansible-playbook, the output just shows each task being run, but it does not show the includes which pull in extra tasks. This makes it hard to how the overall flow jumps around between playbooks. In contrast, include_vars tasks are included in the output. I'm guessing this is because it's an Ansible module, whereas include isn't really a module.

So without having to modify the playbooks, is there way to run playbooks which shows the following?

when include directives are triggering, and
(ideally) also the exact files which are being included, since it's not always obvious how relative paths are converted into absolute paths

I've found lots of advice on various ways to debug playbooks, but nothing which achieves this. Bonus points if it also shows when roles are being included via meta role dependencies!

I'm aware that there are tools such as ansigenome which do static analysis of playbooks, but I'm hoping for something which can output the information at playbook run-time, for any playbook I choose to invoke.

If it's not currently possible, would it be a reasonable feature request?

...

ANSWER

Answered 2017-Aug-30 at 19:15

Try executing ansible-playbook -vv, it shows "task path" for every executed task, like this:

Source https://stackoverflow.com/questions/45967045

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ansigenome

You can install using 'pip install ansigenome' or download it from GitHub, PyPI.
You can use ansigenome like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: