fix: sync command in sui scirpts #949
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Greptile Summary
This PR fixes the
syncPackages
function in the Sui deployment script (sui/deploy-contract.js
). The sync command is responsible for synchronizing local Move package dependencies with deployed contract addresses on the Sui blockchain, ensuring that local development environments reference the correct on-chain package IDs.The changes improve robustness by adding proper error handling for missing packages in the configuration and implementing logic to detect upgraded contracts. When contracts are upgraded on Sui, they receive new package IDs, and syncing these can create dependency conflicts in the Move.toml files. The fix addresses this by:
This change integrates well with the existing Axelar contract deployment infrastructure, which manages complex multi-chain deployments. The sync functionality is critical for maintaining consistency between local development environments and deployed contracts across different blockchain networks.
Important Files Changed
Modified Files
Confidence score: 4/5
Sequence Diagram
ASANA