internet/community.general
3
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2026-05-07 13:52:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove more docs build errors (#45364)

Browse Source 
* orphans testing pages to avoid not-in-toctree errors

* orphans various pages pending reorg

* adds module_utils and special_vars to main TOC

* uses a glob for scenario_guide TOC

* normalize and Sentence-case headings on community pages, typos

* re-orgs community TOC, adds all pages to toctree

* removes scenario guides index page

* adds style guide to community index

* basic update to style guide

* fix typo that created a new error

* removes not-in-toctree from ignore errors list

* leave removing files for future cleanup task
This commit is contained in:
Alicia Cozine
2018-09-11 11:51:47 -05:00
committed by John R Barker
parent 600c7ac108
commit 4264be2b18
32 changed files with 179 additions and 160 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docsite/rst/user_guide/intro.rst
View File

@@ -1,3 +1,5 @@
:orphan:
Introduction
============

5
docs/docsite/rst/user_guide/module_defaults_config.rst
View File

@@ -1,7 +1,10 @@
:orphan:
.. _module_defaults_config:
*****************************
Module Defaults Configuration
=============================
*****************************
Ansible 2.7 adds a preview-status feature to group together modules that share common sets of parameters. This makes
it easier to author playbooks making heavy use of API-based modules such as cloud modules. By default Ansible ships

8
docs/docsite/rst/user_guide/playbook_pathing.rst
View File

@@ -1,6 +1,8 @@
=======================
:orphan:
***********************
Search paths in Ansible
=======================
***********************
Absolute paths are not an issue as they always have a known start, but relative paths ... well, they are relative.
@@ -32,7 +34,7 @@ i.e ::
The current working directory (cwd) is not searched. If you see it, it just happens to coincide with one of the paths above.
If you `include` a task file from a role, it will NOT trigger role behavior, this only happens when running as a role, `include_role` will work.
A new variable `ansible_search_path` var will have the search path used, in order (but without the appended subdirs). Using 5 "v"s (`-vvvvv`) should show the detail of the search as it happens.
A new variable `ansible_search_path` var will have the search path used, in order (but without the appended subdirs). Using 5 "v"s (`-vvvvv`) should show the detail of the search as it happens.
As for includes, they try the path of the included file first and fall back to the play/role that includes them.