refactor(amplifier): standardizes contract config read/write between chain specific and global contracts #397
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.
contractConfig
(e.g. config.axelar.contracts.Gateway.avalanche) andcontractBaseConfig
(e.g. config.axelar.contracts.Gateway), both are equivalent for global contractslastUploadedCodeId
attribute tocontractBaseConfig
codeId
tocontractConfig
--fetchCodeId
option) will updatelastUploadedCodeId
instead ofcodeId
codeId
incontractConfig
codeId
for instantiation/migration (previously setcontractConfig.codeId
will be ignored), in order of priority:--codeId
was set--fetchCodeId
flag was set, it retrieves the code Id from the network by comparing the code hash stored from a governance proposalcontractBaseConfig.lastUploadedCodeId
which was previously set during uploadhttps://axelarnetwork.atlassian.net/browse/AXE-5189