From 4e2014db3d32bd11048999766ce68c05db2a01b6 Mon Sep 17 00:00:00 2001 From: Joseph Torcasso <87090265+jatorcasso@users.noreply.github.com> Date: Wed, 6 Jul 2022 11:59:43 -0400 Subject: [PATCH] Update docs/docsite/rst/dev_guidelines.rst Co-authored-by: Mark Chappell --- docs/docsite/rst/dev_guidelines.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/dev_guidelines.rst b/docs/docsite/rst/dev_guidelines.rst index a08677063f1..bd174f59ff3 100644 --- a/docs/docsite/rst/dev_guidelines.rst +++ b/docs/docsite/rst/dev_guidelines.rst @@ -482,7 +482,7 @@ some response metadata. It is OK to return this to the user as well as they may Boto3 returns most keys in CamelCase. Ansible adopts python standards for naming variables and usage. There is a useful helper function called ``camel_dict_to_snake_dict`` that allows for an easy conversion -of the boto3 response to snake_case. It resides in ``module_utils/common/dict_transformations``. +of the boto3 response to snake_case. It resides in ``ansible.module_utils.``. You should use this helper function and avoid changing the names of values returned by Boto3. E.g. if boto3 returns a value called 'SecretAccessKey' do not change it to 'AccessKey'.