-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Let deployment scripts support some kind of convenient deployment tracking/export facilities like hardhat-deploy
#2550
Comments
I was thinking of implementing this as part of https://github.com/foundry-rs/hardhat A hardhat task that wraps |
Would be awesome! I wrote this discussion post months ago but got busy with work obligations. I am a rust noob but would love to help where possible. #114 |
@tynes are you still working on implementing this feature? It would indeed be super useful! |
No, i've decided that its not the ideal approach and instead opened this issue #3911 Would rather have a higher level |
Any objections to closing this in favor of #3911 as the canonical issue to spec out some higher-level functionality over |
Component
Forge
Describe the feature you would like
Hi! It would be cool if forge deployment scripts supported some kind of convenient deployment tracking/export facilities like hardhat-deploy's export functionality.
As of now, the data/state is already being tracked in
out/
andbroadcast/
indeed! But it's all scattered around. What hardhat-deploy's export does is aggregate the essential deployment data, for a specific chain or for all, into a single file. You can then just drop this json file in your web app and have access to all the deployed contracts' ABI and addresses on the specified chains. It's just kinda handy and easier to automate updates.Additional context
No response
The text was updated successfully, but these errors were encountered: