Great stuff, @Claudio Devecchi ! Do you want to add an OEX app with IPM module for the mongo adapter? BTW, IPM can install necessary Python modules: pymongo etc.

It'd be great to include global name into the YAML file name

Also it'd be great to search/filter globals in the list, ideally with wildcards, e.g. ^Project*

Also, it'd be great to open the tab with the YAML file when clicking on Editor.

Great initiative!

Reading works, but editing and saving doesn't. Created global ^AAA first (in terminal), then read it in VSCode, opened YAML file, edited, saved in /data/gl folder - how can data can be imported to IRIS?

The most thoughtful and clear demos on IRIS - my top preference @Alberto Fuentes! 

I quickly examined https://openexchange.intersystems.com and found an app that seems useful at a first glance. May be @Sergey Mikhailenko can follow up from here. 

Glad this is settled!

I think open-source and private IP policy should be balanced. But Microsoft's financial success and approach which let company to become a largest contributor to open-source could be a good argument that balanced open-source contribution maybe connected to company's prosperity.

Regarding user/pass - it should be a user and his/her password that is allowed to access web app /registry in your IRIS server.

You can go to the list of Web Apps: http://localhost:52773/csp/sys/sec/%25CSP.UI.Portal.Applications.WebList... and observe other and setup your own.

It can be passwordless, basic authentication, bearer token, OAuth, delegated - whatever you decide in your system.

If you are on a community edition of IRIS from a vanilla iris docker image then login/pass you use for your admin access, e.g. to access Management Portal http://localhost:32783/csp/sys/%25CSP.Portal.Home.zen

will work for the registry as well.

There are two steps to publish into a registry. 

1. Load a package into a namespace - you can load from a file directory that contains module.xml, or from a github repo, e.g.

load /folder_with_module/

2. switch to a current registry, where you can publish. You can install your own registry, or use  a test registry, which is always avaliable for different tests:

ZPM:USER>repo -n registry -r -url https://test.pm.community.intersystems.com/registry/ -user test -pass PassWord42

3. Publish a pachage with the command:

publish package_name

Hi @Jani Hurskainen ! Have you solved your question with publishing in a registry?

@Jani Hurskainen , do you have your unittest framework published as open-source by a chance?

Nice workaround! 

@Timothy Leavitt, do we want to consider support alternative unittest framework in IPM client? 

No problem found it https://github.com/intersystems/ipm/releases

First I went to OEX and didn't find it there.

Great news, @Timothy Leavitt!
How can I test the 9.0 beta IPM client?

I see your point, maybe the IRIS package will not help here. But thinking loud I could imagine a user-specific setting that will lock a particular SMP language just for the user you are signing in with. Here the package providing such a functionality could help.

Thank you, @Alexander Koblov !

Sounds like an opportunity for a usefull "addon" package for IRIS, no?