[stdlib] ModuleUpgradeScripts::update_module_upgrade_strategy support set min_time_limit

[jolestar]

ModuleUpgradeScripts::update_module_upgrade_strategy can not support set min_time_limit now.

module ModuleUpgradeScripts {
    public(script) fun update_module_upgrade_strategy(
        sender: signer,
        strategy: u8,
    ){
    //....
     PackageTxnManager::update_module_upgrade_strategy(
            &sender,
            strategy,
            Option::none<u64>(),
        );
   }
}

   // Add a new script function
   public(script) fun update_module_upgrade_strategy_with_min_time(
        sender: signer,
        strategy: u8,
        min_time_limit: u64,
    ){
       //...
      PackageTxnManager::update_module_upgrade_strategy(
            &sender,
            strategy,
            Option::some<u64>(min_time_limit),
        );
   }

[element2050]

support to update the config of the same strategy at the same time.

current stdlib implementation limits this:

            let previous_strategy = get_module_upgrade_strategy(account_address);
            assert(strategy > previous_strategy, Errors::invalid_argument(ESTRATEGY_INCORRECT));

[jolestar]

support to update the config of the same strategy at the same time.

current stdlib implementation limits this:

            let previous_strategy = get_module_upgrade_strategy(account_address);
            assert(strategy > previous_strategy, Errors::invalid_argument(ESTRATEGY_INCORRECT));

update strategy and min time limit only support update once from ARBITRARY to TWO_PHASE.

[element2050]

This means that a contract that has already been deployed and initialized will update the min time limit, can only be redeployed by replacing address ?

[jolestar]

This means that a contract that has already been deployed and initialized will update the min time limit, can only be redeployed by replacing address ?

yes