Evgeny Shvarov

It is on 0.7.3. I use to deploy the folder data/ to a target machine with all the files inside it. In fact it deployed folder and file it contained...

Today we can deploy globals if we have one resource per global. There are real cases when package can contain of hundred+ globals which templated name, similar what is used...

Add support 2025.1 web app CORS settings to generate command

2

Currently generate (or gen) doesn't export new Web App CORS settings appeared in 2025.1: https://docs.intersystems.com/iris20251/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_manage_applications#GSA_manage_application_smpcors Here is what it exports for the app that has such settings: ``` ```

trying to publish an ipm module to a private ipm registry and having the following error

6

zpm:USER>publish demo-loan-frontend [USER|demo-loan-frontend] Initialize START [USER|demo-loan-frontend] Initialize SUCCESS [USER|demo-loan-frontend] Reload START (/home/irisowner/dev/) [USER|demo-loan-frontend] Reload SUCCESS [demo-loan-frontend] Module object refreshed. [USER|demo-loan-frontend] Validate START [USER|demo-loan-frontend] Validate SUCCESS [USER|demo-loan-frontend] Compile START [USER|demo-loan-frontend] Compile...

filecopy deletes file from my repo

2

part of the module.xml: ```xml ``` this produces the following for load command with -v: Loading demo-loan-frontend in process 675 [USER|demo-loan-frontend] Reload START (/home/irisowner/dev/) Skipping preload - directory does not...

Let's have an option to not package unit-tests

1

Currently, when I install a package on a deployed machine, it installs with all the unit tests. Could we have an option in publish command to omit unit-tests? Or maybe...

As CSPApplication tag is deprecated

Support simplified comma-separated list in Match Roles

1

Currently we can put roles a comma separated list but with ":" before every role: MatchRoles=":lovable,:{$dbrole}" Why this ":"? Let's also support the simpler option without ":" like: MatchRoles="lovable,{$dbrole}"