You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per conversations with HS, we'd like a way to differentiate between installation during build-time (i.e. loading a module in order to package and maybe publish it) vs. deployment-time (i.e. installing a pre-packaged module on an instance).
Example use case:
Certain module configuration should only be performed at deployment time. It may be specified in CPF files or in a class that is in an element in the module.xml. This could include ObjectScript code that should be run before/after an existing lifecycle phase. Many of the same lifecycle phases are run as part of publication and straight installation.
Some ideas from @isc-kiyer: IPM could add this functionality to the Invoke argument, Scope (currently can be empty, test or verify), and change it to a comma-separated list which could include the mode and perhaps custom values. Alternatively, IPM could create a different Invoke argument, CustomScope, paralleling the CustomPhase argument.
The text was updated successfully, but these errors were encountered:
Per conversations with HS, we'd like a way to differentiate between installation during build-time (i.e. loading a module in order to package and maybe publish it) vs. deployment-time (i.e. installing a pre-packaged module on an instance).
Example use case:
Certain module configuration should only be performed at deployment time. It may be specified in CPF files or in a class that is in an element in the module.xml. This could include ObjectScript code that should be run before/after an existing lifecycle phase. Many of the same lifecycle phases are run as part of publication and straight installation.
Some ideas from @isc-kiyer: IPM could add this functionality to the Invoke argument, Scope (currently can be empty, test or verify), and change it to a comma-separated list which could include the mode and perhaps custom values. Alternatively, IPM could create a different Invoke argument, CustomScope, paralleling the CustomPhase argument.
The text was updated successfully, but these errors were encountered: