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

Update role elastic and kibana for latest ansible version #142

Closed
pierrejego opened this issue Jan 7, 2025 · 1 comment · Fixed by #143
Closed

Update role elastic and kibana for latest ansible version #142

pierrejego opened this issue Jan 7, 2025 · 1 comment · Fixed by #143
Assignees

Comments

@pierrejego
Copy link
Member

Current ansible roles from galaxy are not compatible with latest ansible version.

@pierrejego pierrejego self-assigned this Jan 7, 2025
pierrejego added a commit that referenced this issue Jan 7, 2025
Update version in requirement to fit latest ansible version

Installation working and deployement succeded but still some work to do to change defaut folder to store data and logs
el_data_dirs and  es_config

link to #142
landryb pushed a commit that referenced this issue Jan 17, 2025
* Change elastic roles to geerlingguy.elasticsearch role

Update version in requirement to fit latest ansible version

Installation working and deployement succeded but still some work to do to change defaut folder to store data and logs
el_data_dirs and  es_config

link to #142

* add extra vars

Path and logs are already propose as a PR in gueerlingguy repo. Waiting for validation geerlingguy/ansible-role-elasticsearch#95

If not merge in the week I will add a new task to change path and logs value after installed.

* This allow to change logs and data path for elasticsearch

Change requirement to add specific role ( fork from geerlingguy because no response to PR)
@landryb landryb linked a pull request Jan 17, 2025 that will close this issue
@landryb
Copy link
Member

landryb commented Jan 17, 2025

fixed by #143

@landryb landryb closed this as completed Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants