-
Notifications
You must be signed in to change notification settings - Fork 563
feat(templates/cmd): upgrade spm to add 'config' cmd #1417
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
Conversation
to appd. * also make $HOME/config/client.toml configurable through 'init.client' section of chain's Starport config.yml.
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.
LGTM
This is great! The only thing is that by default |
What's your proposition to solve this? Is it using the keyring backend test flag or updating config.toml with test backend? If it is the second option, what if user intentionally wanted to keep |
Optimal solution is switch everything within serve to use the default keyring (os) and making sure it does not break anything. |
If using |
As far as I remember, this is not related to To give more info about this: In the past So you mean we should revert our changes in the templates to not overwrite the keyring backend default as In both cases, user might get promped or asked via terminal for a passphrase when you use |
You mean we should scaffold chains with init.client.keyring-backend: test`? |
This is not good 🥴
That could be an option, even though it looks like something that shouldn't be in the config file by default. |
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.
Works! 🌊
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.
Code looks legit to me outside the lint message
In the meantime, anyway to manually change the produced source-code to compile a binary with the default: os ? |
@RaulBernal CLI takes its default value from The |
Updated spn to 0.1.3 and works!! Thanks @fadeev |
* feat(templates/cmd): upgrade spm to add 'config' cmd to appd. * also make $HOME/config/client.toml configurable through 'init.client' section of chain's Starport config.yml. * default to test * fix * fix * updated changelog * fix config application order * fix Co-authored-by: Denis Fadeev <denis@fadeev.org>
* feat(templates/cmd): upgrade spm to add 'config' cmd (#1417) * feat(templates/cmd): upgrade spm to add 'config' cmd to appd. * also make $HOME/config/client.toml configurable through 'init.client' section of chain's Starport config.yml. * default to test * fix * fix * updated changelog * fix config application order * fix Co-authored-by: Denis Fadeev <denis@fadeev.org> * fix(services/chain): detecting keyring (#1449) * fix(services/chain): detecting keyring when client.toml > keyring-backend used. * fix * fix * default to test kb * fix * fix(services/chain): default home dir for app (#1457) * fix(services/chain): support 0.43.x based chains (#1455) * Apply suggestions from code review * Apply suggestions from code review * feat(pkg/chaincmd/runner): support YAML encoded CLI response (#1468) * feat(pkg/chaincmd/runner): support YAML encoded CLI response * Apply suggestions from code review * fix * fix * fix * fix Co-authored-by: Denis Fadeev <denis@fadeev.org>
* feat(templates/cmd): upgrade spm to add 'config' cmd to appd. * also make $HOME/config/client.toml configurable through 'init.client' section of chain's Starport config.yml. * default to test * fix * fix * updated changelog * fix config application order * fix Co-authored-by: Denis Fadeev <denis@fadeev.org>
* feat(templates/cmd): upgrade spm to add 'config' cmd (ignite#1417) * feat(templates/cmd): upgrade spm to add 'config' cmd to appd. * also make $HOME/config/client.toml configurable through 'init.client' section of chain's Starport config.yml. * default to test * fix * fix * updated changelog * fix config application order * fix Co-authored-by: Denis Fadeev <denis@fadeev.org> * fix(services/chain): detecting keyring (ignite#1449) * fix(services/chain): detecting keyring when client.toml > keyring-backend used. * fix * fix * default to test kb * fix * fix(services/chain): default home dir for app (ignite#1457) * fix(services/chain): support 0.43.x based chains (ignite#1455) * Apply suggestions from code review * Apply suggestions from code review * feat(pkg/chaincmd/runner): support YAML encoded CLI response (ignite#1468) * feat(pkg/chaincmd/runner): support YAML encoded CLI response * Apply suggestions from code review * fix * fix * fix * fix Co-authored-by: Denis Fadeev <denis@fadeev.org>
Added support for
~/.marsd/config/client.toml
and introduced a way to configure it fromconfig.yml
.Now, instead of having to specify flags (for example,
marsd ... --keyring-backend os
) every time you run a blockchain's binary, you can set these flags inconfig.yml
:By default,
starport chain serve
resets the data directory on every file change, but changes frominit.client
are propagated toclient.toml
.To use this feature in an already scaffolded blockchain, upgrade your version of
github.com/tendermint/spm
ingo.mod
tov0.1.3
.