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

Generate a unique Erlang cookie by default #68

Merged
merged 1 commit into from
Feb 26, 2022
Merged

Conversation

kocolosk
Copy link
Member

What this PR does / why we need it:

This relies on new support for the COUCHDB_ERLANG_COOKIE env to generate a Secret that is written down into ~/.erlang.cookie instead of passing the cookie in the ERL_FLAGS. I suppose it would be possible to merge the generated cookie into ERL_FLAGS, but this approach seemed cleaner, more secure, and more maintainable going forward.

Special notes for your reviewer:

Will publish the update chart separately, right now I'd like to merge this in part to test a fix for #67 and see if we can get versions up through 3.6.0 published.

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.

  • Chart Version bumped
  • e2e tests pass
  • Variables are documented in the README.md
  • Chart tgz added to /docs and index updated

This relies on new support for the COUCHDB_ERLANG_COOKIE env to
generate a Secret that is written down into ~/.erlang.cookie instead
of passing the cookie in the ERL_FLAGS. I suppose it would be possible
to merge the generated cookie into ERL_FLAGS, but this approach seemed
cleaner and more maintainable going forward.
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.

None yet

1 participant