You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the hyperlane core deploy command without setting the HYP_KEY environment variable, the CLI prompts for the private key for each chain individually instead of just once. Since there are over 120 chains, this makes the deployment process extremely tedious.
Expected Behavior
The CLI should ask for the private key once and reuse it for all chains during deployment.
Actual Behavior
The CLI repeatedly asks for the private key for every chain in the deployment process.
Steps to Reproduce
Run hyperlane core deploy without setting the HYP_KEY environment variable.
Observe that the CLI prompts for the private key for every chain individually.
Additional Context
If HYP_KEY is set, the deployment works as expected, without prompting for multiple private key entries.
This behavior significantly slows down the deployment process when manually entering the private key.
Attachments
Screenshot of the issue:
Expected behavior (when HYP_KEY is set):
Would be great to know if this is the intended behavior or if a fix is planned! 🚀
The text was updated successfully, but these errors were encountered:
Summary
When using the hyperlane core deploy command without setting the HYP_KEY environment variable, the CLI prompts for the private key for each chain individually instead of just once. Since there are over 120 chains, this makes the deployment process extremely tedious.
Expected Behavior
The CLI should ask for the private key once and reuse it for all chains during deployment.
Actual Behavior
The CLI repeatedly asks for the private key for every chain in the deployment process.
Steps to Reproduce
Additional Context
Attachments
Would be great to know if this is the intended behavior or if a fix is planned! 🚀
The text was updated successfully, but these errors were encountered: