Hardhat Ignition is a declarative deployment system that enables you to deploy your smart contracts without navigating the mechanics of the deployment process.
Sometimes it's useful to have a human readable way of visualizing the "transaction log history" for a deployment.
Solution
In conversation with @alcuadrado he mentioned a good solution to avoid having to duplicate the data would be to add a subcommand to hardhat ignition that would parse the journal files and log to console the relevant bits. This new command could allow filtering the data based on the outputs but also it could be piped to a file or other unix tools for further processing.
In our case the data we would be interested in is:
timestamp
from and to addresses
tx hash
parameters
some form of human readable label that's associated with the action being taken (contract or module name for example)
As an example, this is what our custom deployment system logs when running a deployment:
Describe the feature
Problem
Sometimes it's useful to have a human readable way of visualizing the "transaction log history" for a deployment.
Solution
In conversation with @alcuadrado he mentioned a good solution to avoid having to duplicate the data would be to add a subcommand to
hardhat ignitionthat would parse the journal files and log to console the relevant bits. This new command could allow filtering the data based on the outputs but also it could be piped to a file or other unix tools for further processing.In our case the data we would be interested in is:
As an example, this is what our custom deployment system logs when running a deployment:
Search terms
journal, log