-
Notifications
You must be signed in to change notification settings - Fork 553
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
Setting to save development artifacts and store them in a map #590
Setting to save development artifacts and store them in a map #590
Conversation
_revert handles deleting outdated artifacts
fix: cleaned up clear_deployments
df2d0e3
to
ea7b90e
Compare
clean up tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good overall! A few nit-picks but nothing major.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job on this.
|
||
Brownie will maintain a ``map.json`` file in your ``build/deployment/`` folder that lists all deployed contracts on live networks, sorted by chain and contract name. | ||
|
||
:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:: | |
.. code-block:: json |
I'm not 100% on if json
works - but definitely could be python
or javascript
- just to ensure proper code highlighting.
What I did
closes #576
How I did it
Save deployment artifacts for development networks at build/deployments/dev/
Maintain a deployment map (of all deployments) at build/depoyments/map.json in the form of
How to verify it
build/deployments
Checklist