paritytech / paritytech/testnet-manager
Add feature to set session keys from existing keystore keys
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
The session-key-grabber, already contains logic to get sessions public key as string. We should write the automation to submit the setKeys extrinsic with the Validator/Collator account.
This is an alternative to the rotate_session_keys APIs that generates new keystore keys on the nodes and allows to use statically defined keys (eg. from secret or Vault).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the session-key-grabber under dockerfiles/substrate-session-keys-grabber and trace how it obtains session public keys as strings. Then identify the automation entry point for submitting the setKeys extrinsic with the Validator or Collator account. Done means statically supplied keystore keys can be submitted without generating new node keys, including keys sourced from a secret or Vault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100