Add ability to specify multiple `--input-file`

ryan commented

2025-02-14 04:51:16 +00:00

Owner

Use case: I want the ability to specify --input-file address.json and --input-file nonce.json and have both variables be loaded, but I don't want to necessarily have a 1:1 mapping of address and nonce. This would allow the ability to specify both.

Use case: I want the ability to specify `--input-file address.json` and `--input-file nonce.json` and have both variables be loaded, but I don't want to necessarily have a 1:1 mapping of address and nonce. This would allow the ability to specify both.

ryan added this to the Custody Framework project 2025-02-17 08:45:40 +00:00

ryan added this to the Icepick v0.2.0 milestone 2025-02-17 08:45:43 +00:00

ryan self-assigned this 2025-02-17 08:45:47 +00:00

ryan commented

2025-02-18 07:09:23 +00:00

Author

Owner

this is less pressing than i thought it would be. we don't need the nonce address on the offline machine, and we don't need the payer on the online machine.

ryan closed this issue

2025-02-18 07:09:23 +00:00

anton commented

2025-02-26 08:19:10 +00:00

Owner

This was meant to help us remove the need to use jq:

    * `icepick workflow cosmos generate-address --account $account_id | jq -r .pubkey > $account_id.txt`
        * [38 removes need to use jq](https://git.distrust.co/public/icepick/issues/38)

@ryan

This was meant to help us remove the need to use `jq`: ``` * `icepick workflow cosmos generate-address --account $account_id | jq -r .pubkey > $account_id.txt` * [38 removes need to use jq](https://git.distrust.co/public/icepick/issues/38) ``` @ryan

ryan commented

2025-02-26 20:14:45 +00:00

Author

Owner

Yes, you can still run icepick workflow sol generate-address and put the entire content in $account_id.json, and load the entire thing in icepick workflow sol generate-nonce-account. This was to help with a scenario when using multiple of these files, which doesn't exist.

Yes, you can still run `icepick workflow sol generate-address` and put the entire content in `$account_id.json`, and load the entire thing in `icepick workflow sol generate-nonce-account`. This was to help with a scenario when using _multiple_ of these files, which doesn't exist.

👍 1

ryan commented

2025-02-26 20:15:18 +00:00

Author

Owner

There's no case where you need to load the two files we have - the account, and the nonce account - in the same workflow.

👍 1

Add ability to specify multiple --input-file #38

Add ability to specify multiple `--input-file` #38