-
Notifications
You must be signed in to change notification settings - Fork 21
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
Need support to check proper IRIS license when installing a package #377
Comments
So, I suppose it just requires a specific feature flag in license. Then it can be implemented through the additional attribute in SystemRequirements tag |
Since this will be applicable beyond supply chain, I will leave it to IPM PM to decide the best way forward. I only provided one possible solution. |
I have no access to the slide, so, I just guessed |
Yeah, because I'm not part of the company Well, using description part of the license does not look good, it should be through the Feature Flag $system.License.GetFeature(X) On screenshot it shown as Extended Features |
Thanks for sharing the link. Looks like ideal solution is to make this work: $System.License.IsAppLicensed("isc-supply-chain") somehow. Please work with Bob on the proper solution, and supply chain will follow the same practice. |
I think this is a case for intersystems-community/zpm-registry#66 rather than changes to IPM itself. cc @evshvarov and @isc-rkuszews |
I see two needs here:
|
@kuszewski agreed. |
As we plan to launch new supply chain product through IPM, we would like to check if the IRIS instance has the proper license for the installation. For example, IRIS instance without a proper IRIS for Supply Chain license should not be allowed to install package "isc-supply-chain". See Slide 7 in this ppt file for proposed changes in IRIS for Supply Chain license key, which can be used to verify if an IPM installation should be allowed. https://intersystemscorporation-my.sharepoint.com/:p:/g/personal/mzhou_intersystems_com/EdAvFHy0DHhNvI_ZWvE8pfQB-7fH0nzf26TGqCc1kpDEfQ?e=ZqsES8
The text was updated successfully, but these errors were encountered: