-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[cli] Make large packages module address configurable #15118
[cli] Make large packages module address configurable #15118
Conversation
⏱️ 2h 24m total CI duration on this PR
🚨 1 job on the last run was significantly faster/slower than expected
|
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 good, fun thing was I had an env variable version that I was going to ship, but I needed to configure the new laptop with github support
please run cargo xclippy before shipping PRs, it will save you time!
Ahh I should have messaged you earlier. Yes I think I missed the test case - thanks for pointing that out! |
crates/aptos/src/common/types.rs
Outdated
@@ -2350,4 +2351,16 @@ pub struct ChunkedPublishOption { | |||
/// Use this option for publishing large packages exceeding `MAX_PUBLISH_PACKAGE_SIZE`. | |||
#[clap(long)] | |||
pub(crate) chunked_publish: bool, | |||
|
|||
/// Address of the `large_packages` move module for chunked publishing | |||
#[clap(long)] |
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.
Any reason this is Option instead of just String with a default value at the clap level?
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.
That will be better, I'll fix it. Thanks!
- Added a new command option `--large-packages-module-address` to commands related to Move package publishing. - The default address will be used if no value is provided.
916b8c0
to
7237d82
Compare
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.
Did you test it out on devnet?
@@ -1649,6 +1700,10 @@ async fn is_staging_area_empty(txn_options: &TransactionOptions) -> CliTypedResu | |||
pub struct ClearStagingArea { | |||
#[clap(flatten)] | |||
pub(crate) txn_options: TransactionOptions, | |||
|
|||
/// Address of the `large_packages` move module for chunked publishing |
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.
I would add another line that you only have to override when not on testnet or mainnet
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
✅ Forge suite
|
Description
Added a new
--large-packages-module-address
command option for Move package publishing:aptos move publish
aptos move deploy-object
aptos move upgrade-object
aptos move create-object-and-publish-package
aptos move upgrade-object-package
aptos move clear-staging-area
This option will be used alongside the
--chunked-publish
flag. If provided, the specified large packages module address will be used.Note that the CLI does not verify if the module actually exists at the given address; it will simply abort if an incorrect address is supplied.
The default address will be used if no address is provided.
This feature allows users to utilize the chunked publishing in the localnet testing environment by manually deploying the large_packages.move module.
Example
How Has This Been Tested?