Open nataouze opened 8 months ago
Finally changed the implementation to make it less intrusive: DeploymentsManager.executeDeployScripts
is back to what it was and does not require to run DeploymentsManager.loadDeployScripts
first. The external non-execute
deploy scripts are loaded in DeploymentsManager.db.dependenciesScriptPathBags
and DeploymentsManager.db.dependenciesFuncByFilePath
fields instead which are used in DeploymentsManager.executeDeployScripts
as fallback if tags or scripts are not found from the main scripts folders.
@wighawag it would be great if you could take a look at this
Oh man, this is helpful.
i was looking for this feature, will it be merged?
+1
+1
Fixes #341 and #342
Adds an optional
execute
field in theexternal.contracts
configuration which indicates whether theexternal.contracts.deploy
scripts should be executed (defaults totrue
for retrocompatibilty). If set to false, the external deploy scripts are not executed by default but can be used as tag-based dependencies when running the main (non-external) deploy scripts.DeploymentsManager.executeDeployScripts
signature is changed to accept the parametersscriptPathBags
andfuncByFilePath
as it does not load the deployment tags and functions before execution anymore:DeploymentsManager.loadDeployScripts
must be run first to generate these arguments.