Skip to content
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.

Add elasticseach shield user module #2528

Closed

Conversation

barryib
Copy link
Contributor

@barryib barryib commented Jul 7, 2016

ISSUE TYPE
  • New Module Pull Request
COMPONENT NAME

elasticsearch_shield_user

ANSIBLE VERSION
ansible 2.1.0.0
SUMMARY

This module manage the Elasticsearch shield users in an esusers or esnative realm.
The module replace the elasticsearch_esusers from the PR #1574. Now the module support the new shield api introduced by ES 2.3

For more information refer to shield documentation.

See #2529 for shield role management.

…c and rename it into elasticsearch_shield_user

- Move eslasticsearch_esusers module into database/misc
- Rename eslasticsearch_esusers into elasticsearch_shield_user
- Add support for the shield 2.3 API
@gregdek
Copy link
Contributor

gregdek commented Jul 7, 2016

Thanks @barryib 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.]

@ansibot
Copy link

ansibot commented Dec 6, 2016

This repository has been locked. All new issues and pullrequests 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 pullrequest to the ansible/ansible repo.

@ansibot
Copy link

ansibot commented Apr 11, 2017

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.

@ansibot ansibot closed this Apr 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants