-
Notifications
You must be signed in to change notification settings - Fork 122
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
Fixed tmkms keys import -t for priv_validator #350
Fixed tmkms keys import -t for priv_validator #350
Conversation
It seems like your problem would be resolved by using:
|
Some("base64") => self.import_base64(&contents), | ||
Some(other) => { | ||
status_err!("invalid key type: {}", other); | ||
process::exit(1); | ||
} | ||
None => { | ||
if self.path.ends_with("priv_validator.json") { | ||
if self.path.ends_with("priv_validator_key.json") { |
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.
This part seems OK.
@tony-iqlusion yeah, this worked for me eventually (also adding |
Sounds good! |
Done. Can you check once more? |
@freak12techno can you rebase? |
8c76e9e
to
bdd92a3
Compare
@tony-iqlusion done |
Thank you! |
For now,
tmkms keys import -t priv_validator
results in an error:I've renamed the
json
label topriv_validator
to match the description.Also it seems like the
priv_validator.json
file is nowpriv_validator_key.json
(at least on Persistence on core-1 and on Sentinel on sentinelhub-2 it's this way)