When autostartFuelCore property is set to true, the providedUrl is overridden by that of the local short-lived fuel-core node started by the fuels dev command.
When autostartFuelCore property is set to true, the privateKey is overridden with the consensusKey of the local short-lived fuel-core node started by the fuels dev command.
You can supply a ready-to-go deploy configuration object:
deployConfig: { gasPrice: 1,},
Or use a function for crafting dynamic deployment flows:
If you need to fetch and use configs or data from a remote data source
If you need to use IDs from already deployed contracts — in this case, we can use the options.contracts property to get the necessary contract ID. For example:
deployConfig: async (options:ContractDeployOptions) => {// ability to fetch data remotelyawaitPromise.resolve(`simulating remote data fetch`);// get contract by nameconst { contracts } = options;const contract = contracts.find(({ name }) => {const found = name === MY_FIRST_DEPLOYED_CONTRACT_NAME;return found; });if (!contract) {thrownewError('Contract not found!'); }return { gasPrice:1, storageSlots: [ { key:'0x..',/** * Here we could initialize a storage slot, * using the relevant contract ID. */ value: contract.contractId, }, ], };},