Use build.rs-generated YAML file for configuring workflows #29
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/icepick#29
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
TOML is starting to feel tedious. Until we get the HCL version, YAML is a more concise and more flexible option. I'm not the biggest fan of YAML's bare strings,
yes == true
, and other things, but I am willing to work with it for now.Most of the files will be stored in
crates/icepick/workflows/<module_name>/<workflow_name>.yaml
, which will be automatically parsed bybuild.rs
and added to a configuration file.Additional bonus: adding the ability to have multiple arguments means we can specify
address
,pubkey
, andauthorization_address
for something likeicepick workflow sol generate-nonce-account --input-file account.json
For reference, this system should help with implementing new workflows, since YAML is a much nicer language for implementing these nested structures in.
Closing as we have now fully migrated outside of
icepick.toml
for workflows.