RICAPP - Package Manager
The Package Manager provides the following capabilities around application packages
When this option is used the Package Manager takes a complete build directory and navigates for package elements. These elements are bound into the resultant package bundle. Metadata might be compiled along with a manifest, at the discretion of the developer. The concept of signatures has been raised due to recent events to possibly be a higher priority. Ultimately the package should have a signed token in which a Certificate Authority can be used to obtain the Public Key and verify that the Token was in fact generated by the signer. In the interim it might be enough to provide a manifest with Checksum values for pertinent components.
When this option is used the Package Manager examines a package to verify its structure, according to its version. The signature is verified, which in its initial form may be nothing more than validating checksums for any that are identified in a manifest artifact. If the package is valid and a Model Catalog service point is identified the validated package will be onboarded into the catalog. If a Model Catalog is not specified, then only the status is returned.
When this option is used the Package Manager must be provided an applicationVersionID and a Model Catalog service point. The Package Manager will then be able to update the catalog with data or data references at the discretion of the developer to the catalog.