-
Notifications
You must be signed in to change notification settings - Fork 46
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
Add ability to alias contract addresses when deploying #1248
Comments
This idea was previously proposed in the 2022 CLI redesign: |
Are you imagining adding the alias to the local In the design document you linked, we suggested both |
Yes, I think so, although identifying between global and local configs on individual options feels like we're distinguishing on config at the wrong level. In other commands we have a |
That's my thought, too. I sort of prefer something that purposely doesn't mirror the I want to also call out that this is related to (maybe a blocker for?) @fnando's work on: |
Yup, agreed, that is better, and it makes for a pattern we can apply elsewhere that anytime a command has a |
I have updated the issue description to include that global option. |
Personally, I think having With the proposed solution, I'd need to know which flags have a global equivalent. |
Most of time devs deploy to random new addresses, especially when testing locally or on testnet.
It's somewhat annoying to have to copy and paste an address from the result of a deploy command into following commands like invokes.
Folks are coming up with ways to make this easier by piping the contract ID to a file, and then cat-ing the file later on when they need it.
We could make a similar experience built in to the CLI, by offering the ability to alias contract addresses. We already do this for source accounts and keys so it fits in the existing experience.
It could work like this:
For aliases that need to be written to the global config, a
--alias-global
would be used.The aliasing would make it much easier to script deployment and follow up commands.
The text was updated successfully, but these errors were encountered: