-
Notifications
You must be signed in to change notification settings - Fork 24
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
[0.6.0] EVMConnect StatefulSet #54
Conversation
{{- toYaml . | nindent 6 }} | ||
{{- end }} | ||
|
||
{{- tpl .Values.evmconnect.config.policyEngine . | nindent 4 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that a policy engine is required, but currently only a simple engine has been implemented in the open source.
This template by default configures the simple engine, but offers the ability to customize its config and / or plugin future policy engines.
syncWrites: {{ .Values.evmconnect.config.leveldb.syncWrites }} | ||
|
||
connector: | ||
{{- tpl .Values.evmconnect.config.connector . | nindent 6 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A connector (i.e. the blockchain) is required, and so this template defaults to simply setting the JSONRPC URL of the node to use but offers customizing the connector config if necessary.
Signed-off-by: hfuss <haydenfuss@gmail.com>
Signed-off-by: hfuss <haydenfuss@gmail.com>
Signed-off-by: hfuss <haydenfuss@gmail.com>
Signed-off-by: hfuss <haydenfuss@gmail.com>
15316d2
to
fe9888d
Compare
Closing in favor of #60 |
Workings towards support for FireFly v1.1.x as part of the v0.6.0 chart release, this PR adds support for the new firefly-evmconnect runtime.
Similar to the original
ethconnect
support, this will have the chart deployevmconnect
off to the side of FireFly (for now) as aStatefulSet
. Persistent storage is used forleveldb
. Unlike theethconnect
support, this attempts to offer greater flexibility and allow for a user to somewhat safely configure all of the EVMConnect's config options.Integrating EVMConnect into FireFly's own config will be handled in a separate follow-up PR, where FireFly v1.1.x is supported with the new config format related to namespace isolation.