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
Updating the contracts is a composition of multiple steps. They are listed below. It would be great to have a single script which consumes the following:
Here are the steps which are to be performed
1) beamer config read ..... 1-chainA.deployment.json deployments/state/1-chainA.state # read state of chain A
2) cat deployments/state/1-chainA.state # display state and have a look whats going on
3) beamer config modify deployments/state/1-chainA.state
5) beamer config write ... 1-chainA.deployment.json deployments/state/1-chainA.state /tmp/state/1-chainA.desired # write state of chain A
6) beamer config read ..... 1-chainA.deployment.json deployments/state/1-chainA.state # read state of chain A again
7) cat deployments/state/1-chainA.state # display state and verify that changes have been applied
Additionally, artifact files can be consumed as arguments. Each artifact file represents a chain on which the modification will be tried to be applied.
Additional information
The script expects a certain pattern of files in the respective directories. State files are expected to be named the same as the artifact file, just with the ending .state.json.
Desired files with the ending .desired.json will be stored in /tmp/beamer/state/ directory as they are considered to be temporary in the course of updating the contracts.
In the event of already existing state files (updated twice during system run time, the desired file simply gets overwritten.
If state files already exist, they get consumed by the beamer config read command and are updated accordingly.
The end state are updated contracts, and updated state files.
The script should read after the write command and run a verification process if new state and desired state match
What if modification does not change the current state? The script should stop after the read process. The modify command should notice this and tell the user that modifications to not apply any changes.
Allow a -v option to pretty print state after reading
The text was updated successfully, but these errors were encountered:
Updating the contracts is a composition of multiple steps. They are listed below. It would be great to have a single script which consumes the following:
Here are the steps which are to be performed
Options for the commans
Additionally, artifact files can be consumed as arguments. Each artifact file represents a chain on which the modification will be tried to be applied.
Additional information
.state.json
..desired.json
will be stored in/tmp/beamer/state/
directory as they are considered to be temporary in the course of updating the contracts.beamer config read
command and are updated accordingly.-v
option to pretty print state after readingThe text was updated successfully, but these errors were encountered: