Bug fix release.

• Properly interpret ROBOCOPY return codes
• Fix a regression that prevented installation of certain packages

• Support for requirements.txt to use and deploy python's modules
• Tokens for packages publishing support
• Fixed various issues

Learn more in the release notes

• support for deployed packages, installation, and publishing
• support for multiple registry servers, e.g. public community registry, private corporate, and so on
• expanded limit for the length of arguments in Invoke
• the ability to show all versions and package origin in search
• fixed issue for packages with preload code

• token modifier for repo command
• with token param you can authenticate on registry servers that requires authkey (e.g. pm.intersystems.com)
• proxy mode - create https_proxy environment variable if you need to use proxy
• fix passing params and other bugs
• code optimization

changelog

• Various changes in the output command of help
• Changes in colors in the outputs
• Added an ability to add more repo types
• Added an ability to specify a post-installation message, with AfterInstallMessage tag in module.xml
• Added variable ${webroot}, which refers to url with host and port where the internal web-server is available
• Fixed issue when during install if no module was specified (issue #243)
• Fixed issue with uppercased FileCopy resource
• Some other minor bugfixes

The key features of the ZPM 0.2.14 release are:

• Publishing timeout option
• Embedded vars usage in module parameters
• Package installation from Github repo
• Transaction support for install, load and publish.

Here are the release notes.

The timeout issue is fixed.

File copy fix

Improvements and fixes to FileCopy

1. FileCopy

Added some improvements to already existing tag FileCopy

Example of module.xml

<?xml version="1.0" encoding="UTF-8"?>
<Export generator="Cache" version="25">
  <Document name="test-binary.ZPM">
    <Module>
      <Name>test-binary</Name>
      <Version>0.0.1</Version>
      <Packaging>module</Packaging>
      <SourcesRoot>src</SourcesRoot>
      <FileCopy Name="lib" Target="${libdir}my-lib"/> <!-- Copies content of lib folder to target -->
      <FileCopy Name="somefile.jar" Target="${libdir}my-lib"/> <!-- Copies just desired file to target -->
    </Module>
  </Document>
</Export>

Added aliases Target and Dest to attribute InstallDirectory
Supports files as well as directories, no wildcards, just folder content of which should be copied, or particular file
${libdir}, ${bindir} added, installdir/lib and installdir/bin respectively.
Using bindir in docker environments may cause to security issues during install. ${libdir} works in with docker.

2. Invoke improvements

Don't need wrapper tag anymore
Added a few more attributes:

CheckStatus (Default: false), expects that invoked method returns %Status, and use it to check the status of installation.
Phase, (Default: Configure), the phase during which it should be executed
When, (Default: After), values: Before and After. To execute before or after the main execution for the phase
added support for variables, added ${verbose} variable

<Invoke Class="%EnsembleMgr" Method="EnableNamespace" Phase="Compile" When="Before" CheckStatus="true">
  <Arg>${namespace}</Arg>
  <Arg>${verbose}</Arg>
</Invoke>

New in this release:

1)** Interoperability support** - support for dtl, bpl, lut, esd, x12 in module.xml

Now it's allowed to refer to DTL and BPL files. ZPM stores and uses them as CLS.

    <Resource Name="ResourceTest.TestDTL.dtl"/>
    <Resource Name="ResourceTest.TestBPL.bpl"/>

Other interoperability components such as LUT, ESD, X12 should be in XML format  with .xml extension and expected in the folder named i14y (short form of interoperability)

    <Resource Name="Test_HIPAA_5010.X12"/>
    <Resource Name="hl7_2.5.LUT"/>

2) InterSystems BI - DFI files support

Allows multiple ways of defining InterSystems BI (DeepSee) DFI resources
By Fullname

<Resource Name="Sample Operational Reports-Auditing Overview.dashboard.DFI"/>

Wildcard with the folder name

<Resource Name="Sample Operational Reports-*.DFI"/>

Just everything

<Resource Name="*.DFI"/>

Limited by keywords, used only during the export.

<Resource Name="*.DFI" Keywords="myapp"/>

Search command enhancements:

search -d - shows package description
search zpm* - shows packages with names starts with "zpm"

$zpm function

set sc=$zpm("install bla")

Now .DFI resources in xml format supported.

1. fix bugs, including #104
2. <SystemRequirements> - new tag in modul.xml to
   specify required IRIS version
   and production enabled for a module

<SystemRequirements Version=">=2020.1" Interoperability="enabled" />

1. Official test server

To check if your package is published in the registry and then installed from it, use the test registry: https://test.pm.community.intersystems.com/registry/
login: test
password: test

To switch to the test registry use the command
repo -r -n registry -url https://test.pm.community.intersystems.com/registry/ -user test -pass test

Once a day, the test registry is updated and all data in it is reset

2. New commands for the most frequent actions with the module

Previously, to publish a module in the current registry, you had to use the module-action command, for example module-action mymodule publish, and it could be written shorter mymodule publish.

Now you can use the publish command: publish mymodule - use the organic word order

New commands:

• reload
• compile
• test
• package
• verify
• publish

3. Generate command

Using the generate command, you can create a module.xml file template in a second.

Usage:

• generate -template /my/project
  Creates a module.xml file with fictional data in /my/project
  
  After that you must open and edit this file to change module meta information and specify module resources (classes, csp pages, globals, test)

• generate /my/project
  Without -template (or -t) flag this command creates a module.xml file in an interactive mode. Just answer several questions. Use -author (-a) flag to add information about module author

zpm: USER>generate /temp/zzzz

Enter module name: zzzz
Enter module version: 1.0.0 => 1.0.1
Enter module description: module description
Enter module keywords: module keywords
Enter module source folder: src => 

Existing Web Applications:
    /csp/user
    Enter a comma separated list of web applications or * for all: /csp/user
    Enter path to csp files for /csp/user:  src/web
Dependencies:
    Enter module:version or empty string to continue: sslclient:1.0.1
    Enter module:version or empty string to continue: 
zpm: USER>

4. Globals location

Now Globals are expected in /src/gbl (but not in /gbl )

5. Version command

Version command displays currently installed zpm version number; shows locally installed zpm registry and connected remote repository and their version.

zpm: USER>version

 zpm 0.2.2
 Locally installed zpm-registry not found
https://pm.community.intersystems.com - 0.0.2

6. Reset Username and password while switching to another remote repository

If you do not specify the username and password modifiers in the repo command for the remote registry, the previously set values for username and password will be reset.

zpm: USER>repo -r -n registry -url https://pm.community.intersystems.com/

fixed bug with getting the latest version of the package

1. Show module repository
   Use -show-repo modifier with search command to show repositories
   zpm: USER>search -show-repo

2. CSP Applications
   For REST applications no longer need to specify attributes: Directory and Path

3. Custom parameters to modules installation support
   Add Default element in the module.xml to define a parameter and default value

      <Defaults>
        <Default Name="count" Value="7" />       
      </Defaults>

Use parameters in module.xml as ${count}
In install command use -Dcount=42 to pass a new value

4. Wiki documentation is added

5. Fix issue when extracted file size less than original
   Read and discuss all the release news

1. Show module repository
   Use -show-repo modifier with search command to show repositories
   zpm: USER>search -show-repo

2. CSP Applications
   For REST applications no longer need to specify attributes: Directory and Path

3. Custom parameters to modules installation support
   Add Default element in the module.xml to define a parameter and default value

      <Defaults>
        <Default Name="count" Value="7" />       
      </Defaults>

Use parameters in module.xml as ${count}
In install command use -Dzpm.count=42 to pass a new value

4. Wiki documentation is added

5. Fix analytics issue

What’s new:

• Repositories' URLs for the modules, installed via Open Exchange
• Modules analytics support
• OS-level scripting and error reporting
• Bug fixes and small enhancements
• See the solved issues in the current kanban

1. Added synonyms to Path and Directory parameters of CSPApplication
   SourcePath=Path
   DeployPath=Directory

2. ${parameter} supported:
   ${namespace}
   ${mgrdir}
   ${cspdir}
   ${root}
   ${dbrole}

3. search command introduced to show the available modules in a current remote registry
   zpm:USER>search
   moduleX 1.0.0
   moduleY 1.0.0

4. test reporting issues fixed

Tests can run in test and verify phases
Tests with same root don't run twice
Support for running test suites
Support for JUnit output
Inversion of control to support TestCoverage

New simplified sourcecode folder structure is supported.

Updated the Download link

invoke introduced

using auto-publishing