Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support different modes for build and deployment #633

Open
isc-eneil opened this issue Nov 26, 2024 · 0 comments
Open

Support different modes for build and deployment #633

isc-eneil opened this issue Nov 26, 2024 · 0 comments
Labels
enhancement New feature or request prio: medium
Milestone

Comments

@isc-eneil
Copy link
Collaborator

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.

@isc-eneil isc-eneil added enhancement New feature or request prio: high labels Nov 26, 2024
@isc-eneil isc-eneil added this to the Backlog milestone Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request prio: medium
Projects
Status: To do
Development

No branches or pull requests

2 participants