For blockchains that have an execution and consensus layer client, automate JWT creation #115
Labels
meta:good-first-issue
Good for newcomers
meta:triaged
This issue has been triaged (has a good description, as well as labels for priority, size and type)
p3
Low priority
size:medium
Medium
type:feature
New or enhanced functionality
For blockchains like Ethereum, that typically have two clients and a JWT for authentication purposes, we currently require that either a literal value is passed, or an existing secret. For consensus layer charts, we could have an option where the JWT is generated and created as a secret, so that only the secret name must be passed in the dependent (execution layer) chart values.
The text was updated successfully, but these errors were encountered: