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

Move privkey config from node_X.toml to ENV variable #1186

Closed
serejke opened this issue May 16, 2023 · 1 comment · Fixed by #1192
Closed

Move privkey config from node_X.toml to ENV variable #1186

serejke opened this issue May 16, 2023 · 1 comment · Fixed by #1192
Assignees

Comments

@serejke
Copy link

serejke commented May 16, 2023

Contact Details

No response

Propose-a-new-feature

Now that node_X.toml files contain only one secret privkey (there used to be also mnemonic and cross_client.pk but you have removed them), it becomes reasonable to move privkey from the toml file to an ENV variable.

We run Axon nodes in EKS cluster and use CSI Driver to mount secrets from AWS Secrets Manager into the pod.

Alternatives you've considered

Describe alternatives you've considered:

Even more robust solution would be to support the remote AWS signer (#1136), but it is unfeasible right now because AWS KMS does not support BLS cryptography.

Anything else?

No response

@github-actions
Copy link

Hello @driftluo. Please develop this feature.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants