This is a common step for both fund creation and fund migration. It can be triggered by calling either
FundDeployer.createMigratedFundConfig() , respectively.
Both of these functions create all release-level fund configuration at their outsets. This ordered steps are:
FundDeployer deploys a new
ComptrollerProxy instance, which sets the caller-provided core config via
If the caller has provided configuration for an Extension (fees or policies), it then calls
ComptrollerLib.configureExtensions() with the caller-provided config.