Conversation
0a11eb6
to
c54b7e6
Compare
Thanks @jtyr for this new module. When this module receives 'shipit' comments from two community members and any 'needs_revision' comments have been resolved, we will mark for inclusion. [This message brought to you by your friendly Ansibull-bot.] |
shipit Works great for me (compared to the original one, which doesn't) |
I have tested this module with a few Ansible roles with different options, it seems to work as expected, grat job. shipit |
requirements: | ||
- python-ldap | ||
options: | ||
'...': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we normally document this as _raw_params
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would actually prefer an 'entry/object' which is a freeform dict
description: | ||
- Option used to allow the user to overwrite any of the other | ||
options. To remove an option, set the value of the option to | ||
C(null). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this description is very confusing
- simpleSecurityObject | ||
- organizationalRole | ||
description: An LDAP administrator | ||
userPassword: "{SSHA}tabyipcHzhwESzRaGA7oQ/SDoBZQOGND" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see my point above, this seems confusing as the 'non existing options' are slurped into the entry definitions, there is no clear separation between the ldap entry properties and the task options. A simple misspelling will also create havok on entries.
prams: hello=kitty
@jtyr A friendly reminder: this pull request has been marked as needing your action. If you still believe that this PR applies, and you intend to address the issues with this PR, just let us know in the PR itself and we will keep it open pending your changes. When you do address the issues, please respond with ready_for_review in your comment, so that we can notify the maintainer. [This message brought to you by your friendly Ansibull-bot.] |
@jtyr Nice work with the |
@drybjed Yes, the tasks using the old version of the module must be modified. Fortunately it's quite simple - just add the |
@jtyr I have checked the new
The task fails with:
Any idea what attributes would be needed? I checked this on the NB, this is also one of the examples in the module documentation, more or less. |
Thanks for running the tests, @drybjed. I have removed the requirement for having some |
@jtyr Great, looks like it works now, after the necessary changes to tasks are applied. I'm going to switch my copy of shipit |
@jtyr Another friendly reminder: this pull request has been marked as needing your action. If you still believe that this PR applies, and you intend to address the issues with this PR, just let us know in the PR itself and we will keep it open. If you have addressed the issues and believe it's ready for review, please comment with the text "ready_for_review". If we don't hear from you within another 14 days, we will close this pull request. [This message brought to you by your friendly Ansibull-bot.] |
This repository has been locked. All new issues and pull requests should be filed in https://github.com/ansible/ansible Please read through the repomerge page in the dev guide. The guide contains links to tools which automatically move your issue or pull request to the ansible/ansible repo. |
ISSUE TYPE
New Module Pull Request
COMPONENT NAME
ldap_entry
ANSIBLE VERSION
For Ansible 2.3
SUMMARY
This PR is adding a new module that allows to add/change/remove LDAP entries. The module is based on the code from Peter Sagerson who gave me the permission to publish it.