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

Fix kibana password #99

Closed

Conversation

joerg
Copy link

@joerg joerg commented Jan 27, 2015

Do not use, or better misuse, run_state in this case. It does not work this way, so better just use attribute?
This also fixes Issue #55.

Do not use, or better misuse, run_state in this case. It does not work this way, so better just use attribute?
@joerg
Copy link
Author

joerg commented Jan 28, 2015

I have no experience so far with Jenkins and this build failure, but it seems that this error is completely unrelated to my pull request...

@martinb3
Copy link
Contributor

@joerg I'm going to move this into #102. Just for some background:

Elkstack is designed to treat Kibana credentials as data not truly owned by the stack. Many users will end up putting nginx configurations that protect Kibana with ldap, htaccess, SAML, etc, and elkstack is intended to remain agnostic about those decisions. node.run_state is intended for transient data, so elkstack expects wrapper cookbooks to own the credentials data, but pass it to elkstack via node.run_state as transient data. Elkstack guarantees it won't persist that data anywhere -- the responsibility lies on the wrapper cookbooks for that.

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 this pull request may close these issues.

2 participants