bitcoindevkit / bitcoindevkit/bdk-cli

Support parameter override

Open
#271 4 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
141
Forks
99
Avg merge
6d 14m
Merged PRs (30d)
1

Description

**Describe the enhancement**
The config setup forces users to parse toml files or manually modify them to change things like rpc credentials.
Some users might not need modification of these, but in some setups these change continuously, forcing the user to use other tools to modify these files, adding additional dependencies to the setup.

**Use case**
I'm using bdk-cli mainly for testing. Maybe there is a good reason to not give too much freedom to the user to change parameters of their configuration, but I think at least RPC parameters are certainly prone to change, even more if the node is using cookie authentication.

**Additional context**
I updated the bdk-cli in the `bdk-sp` nix environment, and it broke most of the commands I was using to wrap bdk-cli. Some of the changes are useful, like writing keys into file, but some others are not, like rpc credentials. I'm starting and stopping this node very frequently and the rpc cookie changes each time. I had to add a tool like `dasel` to modify the parameters I need in the file.

Contributor guide

Open the contributing guide

Research direction

Start with bdk-cli's config setup and the TOML/RPC parameter handling described in the issue, focusing on how RPC credentials and cookie authentication are loaded. Trace the relevant CLI entry points and verify that repeated node restarts can use changed credentials without manual file editing, while preserving existing configuration behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.