Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDS docs don't mention the attributes "endpoint" and "instance" of the return value #37209

Closed
evankroske opened this issue Mar 8, 2018 · 4 comments · Fixed by #49674 or #49989
Closed
Labels
affects_2.4 This issue/PR affects Ansible v2.4 aws cloud docs This issue/PR relates to or includes documentation. easyfix This issue is considered easy to fix by aspiring contributors. module This issue/PR relates to a module. support:community This issue/PR relates to code supported by the Ansible community.

Comments

@evankroske
Copy link

ISSUE TYPE
  • Documentation Report
COMPONENT NAME

rds

ANSIBLE VERSION

2.4

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

The attributes "endpoint" and "instance" of the return value of the RDS module aren't documented. The documentation doesn't mention either of them, even though the example code does.

STEPS TO REPRODUCE
  1. Go to http://docs.ansible.com/ansible/latest/rds_module.html#return-values.
EXPECTED RESULTS

Find documentation for "endpoint" and "instance".

ACTUAL RESULTS

Don't find documentation for "endpoint" or "instance".

@ansibot
Copy link
Contributor

ansibot commented Mar 8, 2018

Files identified in the description:

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot
Copy link
Contributor

ansibot commented Mar 8, 2018

@ansibot ansibot added affects_2.4 This issue/PR affects Ansible v2.4 aws cloud docs This issue/PR relates to or includes documentation. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. support:community This issue/PR relates to code supported by the Ansible community. labels Mar 8, 2018
@rcarrillocruz rcarrillocruz removed the needs_triage Needs a first human triage before being processed. label Mar 9, 2018
@ansibot ansibot added support:core This issue/PR relates to code supported by the Ansible Engineering Team. and removed support:community This issue/PR relates to code supported by the Ansible community. labels Sep 17, 2018
@ansibot ansibot added needs_maintainer Ansibot is unable to identify maintainers for this PR. (Check `author` in docs or BOTMETA.yml) support:community This issue/PR relates to code supported by the Ansible community. and removed support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Oct 3, 2018
@ansibot ansibot removed the needs_maintainer Ansibot is unable to identify maintainers for this PR. (Check `author` in docs or BOTMETA.yml) label Nov 10, 2018
@Akasurde Akasurde added the easyfix This issue is considered easy to fix by aspiring contributors. label Nov 15, 2018
@lpkirby lpkirby mentioned this issue Dec 8, 2018
acozine pushed a commit that referenced this issue Dec 10, 2018
Adds endpoint and port to the instance return values for rds.py.  Partial fix for #37209
@lpkirby
Copy link
Contributor

lpkirby commented Dec 11, 2018

@acozine Thank you for the comments on the PR. I could use some guidance on adding the instance part. As far as I can tell, every one of those return values falls under "instance."

Here is the start of the output when I register and debug print the rds output:

 "msg": {
        "changed": false,
        "failed": false,
        "instance": {
          "allocated_storage": 600,
          "auto_minor_version_upgrade": true,
          "availability_zone": "us-east-1a",
          "backup_retention": 7,
      ....

Perhaps just a note showing how all the return values are referenced using the instance dict?

@acozine
Copy link
Contributor

acozine commented Dec 12, 2018

@lpkirby ah, I see - this is a complex return value, where the main key is an instance or list of instances. This is true for a lot of cloud modules.

Here's an example of documenting complex return values:
https://docs.ansible.com/ansible/devel/modules/ec2_ami_facts_module.html#return-values
Source for that example:
https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/ec2_ami_facts.py.

There are more examples, and some tips, in the developer documentation at https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_documenting.html#return-block

@acozine acozine reopened this Dec 12, 2018
lpkirby pushed a commit to lpkirby/ansible that referenced this issue Dec 30, 2018
kbreit pushed a commit to kbreit/ansible that referenced this issue Jan 11, 2019
Adds endpoint and port to the instance return values for rds.py.  Partial fix for ansible#37209
kbreit pushed a commit to kbreit/ansible that referenced this issue Jan 11, 2019
@ansible ansible locked and limited conversation to collaborators Jul 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.4 This issue/PR affects Ansible v2.4 aws cloud docs This issue/PR relates to or includes documentation. easyfix This issue is considered easy to fix by aspiring contributors. module This issue/PR relates to a module. support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants