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.

Sign up for GitHub

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

Jump to bottom

upstream bigip_user #193

Closed
25 tasks done
caphrim007 opened this issue May 15, 2017 · 3 comments
Closed
25 tasks done

upstream bigip_user #193

caphrim007 opened this issue May 15, 2017 · 3 comments
Assignees
@caphrim007 @payalsin
Labels
new-module Issues that require the creation of a new Ansible module upstream Issues for modules that need to be upstreamed due to bugfix, enhancement, or new module
Projects
Ansible 2.4 release

Comments

@caphrim007
Copy link
Contributor

caphrim007 commented May 15, 2017 •
edited

ISSUE TYPE
  • Upstream request
COMPONENT NAME

library/bigip_user.py

ANSIBLE VERSION
ansible 2.4.0
  config file = 
  configured module search path = [u'/Users/trupp/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/trupp/src/envs/ansible-2.0/lib/python2.7/site-packages/ansible
  executable location = /Users/trupp/src/envs/ansible-2.0/bin/ansible
  python version = 2.7.10 (default, Jul 30 2016, 18:31:42) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]
PYTHON VERSION
Python 2.7.10
BIGIP VERSION
  • 12.0.0 (BIGIP-12.0.0.0.0.606)
  • 12.1.0 (BIGIP-12.1.0.0.0.1434)
  • 12.1.0-hf1 (BIGIP-12.1.0.1.0.1447-HF1)
  • 12.1.0-hf2 (BIGIP-12.1.0.2.0.1468-HF2)
  • 12.1.1 (BIGIP-12.1.1.0.0.184)
  • 12.1.1-hf1 (BIGIP-12.1.1.1.0.196-HF1)
  • 12.1.1-hf2 (BIGIP-12.1.1.2.0.204-HF2)
  • 12.1.2 (BIGIP-12.1.2.0.0.249)
  • 12.1.2-hf1 (BIGIP-12.1.2.1.0.264-HF1)
  • 13.0.0 (BIGIP-13.0.0.0.0.1645)
CHECKLIST
  • Playbook exists to do functional tests
  • Docs exist and build correctly (make docs)
  • Role directory with functional tests exists
  • Unit tests in tests/unit for the product exist
  • TestParameters unit test class exists and has content
  • TestManager unit test class exists and has contents
  • Module code has EXAMPLES
  • Module code has DOCUMENTATION
  • Module code has RETURN
  • Module code has ANSIBLE_METADATA
  • Module code has been tested on major releases post 12.x. If a major release cannot be supported, document "why" in the notes section of the module
    DOCUMENTATION
  • Module code conforms to coding standards (v3). This includes a Parameters class, ModuleManager class, and ArgumentSpec class.
  • Module code passes tox -e flake -- library/MODULE_NAME.py
  • Unit test code passes tox -e flake -- test/unit/PRODUCT/test_MODULE_NAME.py
  • Module includes GPL3 license at top of the file and F5 Networks copyright.
SUMMARY
@caphrim007 caphrim007 added the upstream Issues for modules that need to be upstreamed due to bugfix, enhancement, or new module label May 15, 2017
@payalsin payalsin mentioned this issue May 16, 2017
Closed
@caphrim007
Copy link
Contributor Author

@payalsin I've verified all of the above. moving on to upstreaming

@caphrim007
Copy link
Contributor Author

ansible/ansible#24753

@caphrim007
Copy link
Contributor Author

@payalsin this is now complete

ansible/ansible#24753

@caphrim007 caphrim007 moved this from Todo to Done in Ansible 2.4 release May 19, 2017
@caphrim007 caphrim007 added the new-module Issues that require the creation of a new Ansible module label Jun 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@caphrim007 caphrim007

@payalsin payalsin

Labels
new-module Issues that require the creation of a new Ansible module upstream Issues for modules that need to be upstreamed due to bugfix, enhancement, or new module
Projects
No open projects
Ansible 2.4 release
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@caphrim007 @payalsin