From 5dcb20dfdba9a3c28e3325978bd98c5aa67cc14b Mon Sep 17 00:00:00 2001 From: Ed Costello Date: Tue, 11 Jun 2019 02:56:28 +1200 Subject: [PATCH] Replace links to AWS module guidelines with links to devel docsite since (#57466) the GUIDELINES.md has been moved to the docsite. --- .../docsite/rst/dev_guide/developing_modules_best_practices.rst | 2 +- docs/docsite/rst/dev_guide/index.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst index 6414c1eb55e..2a4aae2ff8d 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst @@ -150,7 +150,7 @@ Ansible conventions offer a predictable user interface across all modules, playb * Implement declarative operations (not CRUD) so the user can ignore existing state and focus on final state. For example, use ``started/stopped``, ``present/absent``. * Strive for a consistent final state (aka idempotency). If running your module twice in a row against the same system would result in two different states, see if you can redesign or rewrite to achieve consistent final state. If you can't, document the behavior and the reasons for it. * Provide consistent return values within the standard Ansible return structure, even if NA/None are used for keys normally returned under other options. -* Follow additional guidelines that apply to families of modules if applicable. For example, AWS modules should follow `the Amazon guidelines `_ +* Follow additional guidelines that apply to families of modules if applicable. For example, AWS modules should follow `the Amazon guidelines `_ Module Security =============== diff --git a/docs/docsite/rst/dev_guide/index.rst b/docs/docsite/rst/dev_guide/index.rst index d738a74ef12..25189e99c5d 100644 --- a/docs/docsite/rst/dev_guide/index.rst +++ b/docs/docsite/rst/dev_guide/index.rst @@ -20,7 +20,7 @@ Find the task that best describes what you want to do: * I want to :ref:`set up my Python development environment `. * I want to :ref:`get started writing a module `. * I want to :ref:`write a Windows module `. - * I want to `write an Amazon (AWS) module `_. + * I want to `write an Amazon (AWS) module `_. * I want to :ref:`write a series of related modules ` that integrate Ansible with a new product (for example, a database, cloud provider, network platform, etc.). * I want to refine my code: