diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-ansible-navigator.spec | 472 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 474 insertions, 0 deletions
@@ -0,0 +1 @@ +/ansible-navigator-3.2.0.tar.gz diff --git a/python-ansible-navigator.spec b/python-ansible-navigator.spec new file mode 100644 index 0000000..b76b670 --- /dev/null +++ b/python-ansible-navigator.spec @@ -0,0 +1,472 @@ +%global _empty_manifest_terminate_build 0 +Name: python-ansible-navigator +Version: 3.2.0 +Release: 1 +Summary: A text-based user interface (TUI) for the Red Hat Ansible Automation Platform +License: Apache +URL: https://pypi.org/project/ansible-navigator/ +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/cd/f8/1ff54e1883b2e1a56b650c1a12ce6347f11d4726431835a46d3119a2504f/ansible-navigator-3.2.0.tar.gz +BuildArch: noarch + +Requires: python3-ansible-builder +Requires: python3-ansible-runner +Requires: python3-jinja2 +Requires: python3-jsonschema +Requires: python3-onigurumacffi +Requires: python3-pyyaml +Requires: python3-tzdata +Requires: python3-importlib-metadata +Requires: python3-setuptools +Requires: python3-mkdocs-ansible +Requires: python3-ansible-core +Requires: python3-coverage-enable-subprocess +Requires: python3-coverage[toml] +Requires: python3-darglint +Requires: python3-flake8-docstrings +Requires: python3-libtmux +Requires: python3-pre-commit +Requires: python3-pytest-mock +Requires: python3-pytest-plus +Requires: python3-pytest-subtests +Requires: python3-pytest-xdist +Requires: python3-typing-extensions + +%description +# ansible-navigator + +[//]: # (DO-NOT-REMOVE-docs-intro-START) + +A text-based user interface (TUI) for Ansible. + +A demo of the interface can be found [on YouTube][YT demo]. + +[YT demo]: https://www.youtube.com/watch?v=J9PBKi8ydi4 + +[//]: # (DO-NOT-REMOVE-docs-intro-END) + +## Quick start + +### Installing + +Getting started with ansible-navigator is as simple as: + +``` +pip3 install 'ansible-navigator[ansible-core]' +ansible-navigator --help +``` + +(Users wishing to install within a virtual environment might find the relevant +[Python documentation][Python venv doc] useful.) + +By default, ansible-navigator uses a container runtime (`podman` or `docker`, +whichever it finds first) and runs Ansible within an execution environment +(a pre-built container image which includes [ansible-core] along with a set +of Ansible collections.) + +This default behavior can be disabled by starting ansible-navigator with +`--execution-environment false`. In this case, Ansible and any collections +needed must be installed manually on the system. + +[ansible-core]: https://docs.ansible.com/ansible-core/devel +[Python venv doc]: https://docs.python.org/3/library/venv.html + +Additional `Linux`, `macOS` and `Windows with WSL2` installation +instructions are available in the [Installation guide]. + +[Installation guide]: +https://ansible-navigator.readthedocs.io/installation/ + +## Welcome + +When running `ansible-navigator` with no arguments, you will be presented with +the *welcome page*. From this page, you can run playbooks, browse collections, +explore inventories, read Ansible documentation, and more. + +A full list of key bindings can be viewed by typing `:help`. + +## Output modes + +There are two modes in which ansible-navigator can be run: + +* The **interactive** mode, which provides a curses-based user interface and + allows you to "zoom in" on data in real time, filter it, and navigate between + various Ansible components; and +* The **stdout** mode, which does *not* use curses, and simply returns the + output to the terminal's standard output stream, as Ansible's commands + would. + +The **interactive** mode is the default and this default can be overwritten by +passing `--mode stdout` (`-m stdout`) or setting `mode` in +[configuration][settings documentation]. + +[settings documentation]: https://ansible-navigator.readthedocs.io/settings/ + +## Example commands + +All of ansible-navigator's features can be accessed from the *welcome page* +described above, but as a shortcut, commands can also be provided directly as +command-line arguments. + +Some examples: + +* Review and explore available collections: `ansible-navigator collections` +* Review and explore current Ansible configuration: `ansible-navigator config` +* Review and explore Ansible documentation: + `ansible-navigator doc ansible.netcommon.cli_command` +* Review execution environment images available locally: + `ansible-navigator images` +* Review and explore an inventory: + `ansible-navigator inventory -i inventory.yaml` +* Run and explore a playbook: + `ansible-navigator run site.yaml -i inventory.yaml` + +Or using the **stdout** mode described above: + +* Show the current Ansible configuration: + `ansible-navigator config dump -m stdout` +* Show documentation: `ansible-navigator doc sudo -t become -m stdout` + +... and so on. A full list of subcommands and their relation to Ansible +commands can be found in the [subcommand documentation]. + +[subcommand documentation]: +https://ansible-navigator.readthedocs.io/subcommands/ + +## Configuring ansible-navigator + +There are several ways to configure ansible-navigator and users and projects +are free to choose the most convenient method for them. The full hierarchy of +how various configuration sources are applied can be found in the FAQ mentioned +below. + +Of note, projects making use of ansible-navigator can include a project-wide +configuration file with the project. If one is not found, ansible-navigator +will look for a user-specific configuration file in the user's home directory. +Details about this can be found in the [settings documentation]. + +## Frequently Asked Questions (FAQ) + +We maintain a [list of common questions][FAQ] which provides a good +resource to check if something is tripping you up. We also encourage additions +to this document for the greater community! + +[FAQ]: https://ansible-navigator.readthedocs.io/faq/ + +## License + +ansible-navigator is released under the Apache License version 2. See the +[LICENSE] file for more details. + +[LICENSE]: https://github.com/ansible/ansible-navigator/blob/main/LICENSE + + +%package -n python3-ansible-navigator +Summary: A text-based user interface (TUI) for the Red Hat Ansible Automation Platform +Provides: python-ansible-navigator +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-ansible-navigator +# ansible-navigator + +[//]: # (DO-NOT-REMOVE-docs-intro-START) + +A text-based user interface (TUI) for Ansible. + +A demo of the interface can be found [on YouTube][YT demo]. + +[YT demo]: https://www.youtube.com/watch?v=J9PBKi8ydi4 + +[//]: # (DO-NOT-REMOVE-docs-intro-END) + +## Quick start + +### Installing + +Getting started with ansible-navigator is as simple as: + +``` +pip3 install 'ansible-navigator[ansible-core]' +ansible-navigator --help +``` + +(Users wishing to install within a virtual environment might find the relevant +[Python documentation][Python venv doc] useful.) + +By default, ansible-navigator uses a container runtime (`podman` or `docker`, +whichever it finds first) and runs Ansible within an execution environment +(a pre-built container image which includes [ansible-core] along with a set +of Ansible collections.) + +This default behavior can be disabled by starting ansible-navigator with +`--execution-environment false`. In this case, Ansible and any collections +needed must be installed manually on the system. + +[ansible-core]: https://docs.ansible.com/ansible-core/devel +[Python venv doc]: https://docs.python.org/3/library/venv.html + +Additional `Linux`, `macOS` and `Windows with WSL2` installation +instructions are available in the [Installation guide]. + +[Installation guide]: +https://ansible-navigator.readthedocs.io/installation/ + +## Welcome + +When running `ansible-navigator` with no arguments, you will be presented with +the *welcome page*. From this page, you can run playbooks, browse collections, +explore inventories, read Ansible documentation, and more. + +A full list of key bindings can be viewed by typing `:help`. + +## Output modes + +There are two modes in which ansible-navigator can be run: + +* The **interactive** mode, which provides a curses-based user interface and + allows you to "zoom in" on data in real time, filter it, and navigate between + various Ansible components; and +* The **stdout** mode, which does *not* use curses, and simply returns the + output to the terminal's standard output stream, as Ansible's commands + would. + +The **interactive** mode is the default and this default can be overwritten by +passing `--mode stdout` (`-m stdout`) or setting `mode` in +[configuration][settings documentation]. + +[settings documentation]: https://ansible-navigator.readthedocs.io/settings/ + +## Example commands + +All of ansible-navigator's features can be accessed from the *welcome page* +described above, but as a shortcut, commands can also be provided directly as +command-line arguments. + +Some examples: + +* Review and explore available collections: `ansible-navigator collections` +* Review and explore current Ansible configuration: `ansible-navigator config` +* Review and explore Ansible documentation: + `ansible-navigator doc ansible.netcommon.cli_command` +* Review execution environment images available locally: + `ansible-navigator images` +* Review and explore an inventory: + `ansible-navigator inventory -i inventory.yaml` +* Run and explore a playbook: + `ansible-navigator run site.yaml -i inventory.yaml` + +Or using the **stdout** mode described above: + +* Show the current Ansible configuration: + `ansible-navigator config dump -m stdout` +* Show documentation: `ansible-navigator doc sudo -t become -m stdout` + +... and so on. A full list of subcommands and their relation to Ansible +commands can be found in the [subcommand documentation]. + +[subcommand documentation]: +https://ansible-navigator.readthedocs.io/subcommands/ + +## Configuring ansible-navigator + +There are several ways to configure ansible-navigator and users and projects +are free to choose the most convenient method for them. The full hierarchy of +how various configuration sources are applied can be found in the FAQ mentioned +below. + +Of note, projects making use of ansible-navigator can include a project-wide +configuration file with the project. If one is not found, ansible-navigator +will look for a user-specific configuration file in the user's home directory. +Details about this can be found in the [settings documentation]. + +## Frequently Asked Questions (FAQ) + +We maintain a [list of common questions][FAQ] which provides a good +resource to check if something is tripping you up. We also encourage additions +to this document for the greater community! + +[FAQ]: https://ansible-navigator.readthedocs.io/faq/ + +## License + +ansible-navigator is released under the Apache License version 2. See the +[LICENSE] file for more details. + +[LICENSE]: https://github.com/ansible/ansible-navigator/blob/main/LICENSE + + +%package help +Summary: Development documents and examples for ansible-navigator +Provides: python3-ansible-navigator-doc +%description help +# ansible-navigator + +[//]: # (DO-NOT-REMOVE-docs-intro-START) + +A text-based user interface (TUI) for Ansible. + +A demo of the interface can be found [on YouTube][YT demo]. + +[YT demo]: https://www.youtube.com/watch?v=J9PBKi8ydi4 + +[//]: # (DO-NOT-REMOVE-docs-intro-END) + +## Quick start + +### Installing + +Getting started with ansible-navigator is as simple as: + +``` +pip3 install 'ansible-navigator[ansible-core]' +ansible-navigator --help +``` + +(Users wishing to install within a virtual environment might find the relevant +[Python documentation][Python venv doc] useful.) + +By default, ansible-navigator uses a container runtime (`podman` or `docker`, +whichever it finds first) and runs Ansible within an execution environment +(a pre-built container image which includes [ansible-core] along with a set +of Ansible collections.) + +This default behavior can be disabled by starting ansible-navigator with +`--execution-environment false`. In this case, Ansible and any collections +needed must be installed manually on the system. + +[ansible-core]: https://docs.ansible.com/ansible-core/devel +[Python venv doc]: https://docs.python.org/3/library/venv.html + +Additional `Linux`, `macOS` and `Windows with WSL2` installation +instructions are available in the [Installation guide]. + +[Installation guide]: +https://ansible-navigator.readthedocs.io/installation/ + +## Welcome + +When running `ansible-navigator` with no arguments, you will be presented with +the *welcome page*. From this page, you can run playbooks, browse collections, +explore inventories, read Ansible documentation, and more. + +A full list of key bindings can be viewed by typing `:help`. + +## Output modes + +There are two modes in which ansible-navigator can be run: + +* The **interactive** mode, which provides a curses-based user interface and + allows you to "zoom in" on data in real time, filter it, and navigate between + various Ansible components; and +* The **stdout** mode, which does *not* use curses, and simply returns the + output to the terminal's standard output stream, as Ansible's commands + would. + +The **interactive** mode is the default and this default can be overwritten by +passing `--mode stdout` (`-m stdout`) or setting `mode` in +[configuration][settings documentation]. + +[settings documentation]: https://ansible-navigator.readthedocs.io/settings/ + +## Example commands + +All of ansible-navigator's features can be accessed from the *welcome page* +described above, but as a shortcut, commands can also be provided directly as +command-line arguments. + +Some examples: + +* Review and explore available collections: `ansible-navigator collections` +* Review and explore current Ansible configuration: `ansible-navigator config` +* Review and explore Ansible documentation: + `ansible-navigator doc ansible.netcommon.cli_command` +* Review execution environment images available locally: + `ansible-navigator images` +* Review and explore an inventory: + `ansible-navigator inventory -i inventory.yaml` +* Run and explore a playbook: + `ansible-navigator run site.yaml -i inventory.yaml` + +Or using the **stdout** mode described above: + +* Show the current Ansible configuration: + `ansible-navigator config dump -m stdout` +* Show documentation: `ansible-navigator doc sudo -t become -m stdout` + +... and so on. A full list of subcommands and their relation to Ansible +commands can be found in the [subcommand documentation]. + +[subcommand documentation]: +https://ansible-navigator.readthedocs.io/subcommands/ + +## Configuring ansible-navigator + +There are several ways to configure ansible-navigator and users and projects +are free to choose the most convenient method for them. The full hierarchy of +how various configuration sources are applied can be found in the FAQ mentioned +below. + +Of note, projects making use of ansible-navigator can include a project-wide +configuration file with the project. If one is not found, ansible-navigator +will look for a user-specific configuration file in the user's home directory. +Details about this can be found in the [settings documentation]. + +## Frequently Asked Questions (FAQ) + +We maintain a [list of common questions][FAQ] which provides a good +resource to check if something is tripping you up. We also encourage additions +to this document for the greater community! + +[FAQ]: https://ansible-navigator.readthedocs.io/faq/ + +## License + +ansible-navigator is released under the Apache License version 2. See the +[LICENSE] file for more details. + +[LICENSE]: https://github.com/ansible/ansible-navigator/blob/main/LICENSE + + +%prep +%autosetup -n ansible-navigator-3.2.0 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-ansible-navigator -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Mon May 15 2023 Python_Bot <Python_Bot@openeuler.org> - 3.2.0-1 +- Package Spec generated @@ -0,0 +1 @@ +6677d3ce9bba676c027732d9aba3d49e ansible-navigator-3.2.0.tar.gz |