Open isc-eneil opened 1 day ago
Likely minor complication here is going to be unified dependency resolution across the set of modules.
Note from @isc-kiyer in discussion today: most important use case is the flat file multi-namespace orchestration
Note that this is less urgent than the other HS-requested issues because we could ask users to run an install/load command for each module.
Why not manage it via dependencies? e.g. having a "master" module that have a list of dependent modules?
On Tue, Nov 26, 2024 at 2:55 PM isc-eneil @.***> wrote:
Note that this is less urgent than the other HS-requested issues because we could ask users to run an install/load command for each module.
— Reply to this email directly, view it on GitHub https://github.com/intersystems/ipm/issues/630#issuecomment-2501031189, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVHEP7FVGF4J6OUTFLMYXD2CSDXVAVCNFSM6AAAAABSPCEM3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGAZTCMJYHE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
That's an interesting idea. For the HS use case, we are interested in installing one module per namespace. The modules in the "solution pack" are not co-dependent. A master module for our case would break the assumption that module dependencies need to be installed in the same namespace as the module's source code.
Per conversations with HS, we are asking for support for installing and loading multiple modules onto an instance via a single install or load command. It should be possible for the user to specify the namespace into which each module should be installed, ideally via flat file.
This will allow for a "solution pack" that is comprised of several modules to be easily installed.