Registering a Catalog item

In order to make a new Catalog item or a new version of a Catalog item available in the DataMiner Catalog, you need to register it using the Catalog API.

When you register a new Catalog item, it will only become available for the registered organization, and it will be marked as private in the Catalog to indicate this.

A Catalog item is identified by a unique ID (GUID), which you will need to provide yourself.

Important

The API calls are authenticated using organization keys. Make sure you use a key that has the Register Catalog items permission and add it to the HTTP request in a header called Ocp-Apim-Subscription-Key. Also, note that you need to have the Owner role in order to access or create organization keys.

Tip

For practical examples, refer to the tutorials Registering a new connector in the Catalog, Registering a new version of a connector in the Catalog, and Registering a new version of a connector in the Catalog using GitHub Actions.

Registering a Catalog item with workflows and tooling

Create a catalog.yml or manifest.yml file as outlined under Manifest file below.
Generate an organization key with the Register Catalog items permission.
Either use our pre-made workflows on GitHub or platform-independent tooling.
- If you are interested in reusing Skyline's pre-made pipelines, which include quality-of-life features and a robust quality gate, refer to the From code to product tutorial.
- If you would prefer not to use Postman and HTTPS directly, try out our platform-independent Catalog Uploader tool: Catalog Uploader README.
  
  To install and use the tool in any command line or bash:
```
dotnet tool install -g Skyline.DataMiner.CICD.Tools.CatalogUpload
dataminer-catalog-upload update-catalog-details --path-to-catalog-yml "catalog.yml" --path-to-readme "README.md" --path-to-images "resources/images" --dm-catalog-token "abc123"
```

Important

Unlike the API, the platform-independent tooling can operate without a predefined unique ID (GUID). If no ID is provided, it will create a new Catalog record and return the Catalog ID. For subsequent uploads, it is essential to use this returned Catalog ID to avoid creating duplicate records.

Registering a Catalog item with the API

The register API call allows you to create or update a Catalog item. To add a version after you have successfully registered an item, see Registering a new version with the API.

API Definition

For a complete definition of the API, go to Key Catalog API Swagger.

This page also provides a quick way to execute the call: Expand the "catalog/register" item, and click the Try it out button.

Important

Clicking the Try it out button will execute the register call on the production Catalog.

The Swagger.json can be used by e.g. Swagger CodeGen or AutoRest to generate client code.

HTTP method

PUT

Body

The body of the request should be of type multipart/form-data and must contain a key of type File with the name file.

The value of this key should be a .zip file containing the following items:

A manifest.yml file (required).
A README.md file containing the description of the Catalog item (optional).

Tip

See also: Best practices when documenting Catalog items.
An images folder containing any image referenced in the readme file (optional). Supported image extensions are .jpg, .jpeg, .png, .gif, .bmp, .tif, .tiff, and .webp.

file: <the zip file containing manifest, README and optional images>

Note

To reference images in the README.md file, you can use the home directory (~/images) or relative path syntax (./images).

Manifest file

This file will contain all the necessary information to register a Catalog item with a version. This manifest file should be a valid .yml file and will contain "required" and "optional" attributes to add extra information to the Catalog item. Note that limitations may apply to certain attributes based on length or formatting.

# [Required]
# Possible values for the Catalog item that can be deployed on a DataMiner System:
#   - automationscript: If the Catalog item is a general-purpose DataMiner Automation script.
#   - lifecycleserviceorchestration: If the Catalog item is a DataMiner Automation script designed to manage the life cycle of a service.
#   - profileloadscript: If the Catalog item is a DataMiner Automation script designed to load a standard DataMiner profile.
#   - userdefinedapi: If the Catalog item is a DataMiner Automation script designed as a user-defined API.
#   - adhocdatasource: If the Catalog item is a DataMiner Automation script designed for an ad hoc data source integration.
#   - chatopsextension: If the Catalog item is a DataMiner Automation script designed as a ChatOps extension.
#   - connector: If the Catalog item is a DataMiner XML connector.
#   - slamodel: If the Catalog item is a DataMiner XML connector designed as DataMiner Service Level Agreement model.
#   - enhancedservicemodel: If the Catalog item is a DataMiner XML connector designed as DataMiner enhanced service model.
#   - visio: If the Catalog item is a Microsoft Visio design.
#   - solution: If the Catalog item is a DataMiner Solution.
#   - testingsolution: If the Catalog item is a DataMiner Solution designed for automated testing and validation.
#   - samplesolution: If the Catalog item is a DataMiner Solution used for training and education.
#   - standardsolution: If the Catalog item is a DataMiner Solution that is an out-of-the-box solution for a specific use case or application.
#   - dashboard: If the Catalog item is a DataMiner dashboard.
#   - lowcodeapp: If the Catalog item is a DataMiner low-code app.
#   - datatransformer: If the Catalog item is a Data Transformer.
#   - dataquery: If the Catalog item is a GQI data query.
#   - functiondefinition: If the Catalog item is a DataMiner function definition.
#   - scriptedconnector: If the Catalog item is a DataMiner scripted connector.
#   - bestpracticesanalyzer: If the Catalog item is a DataMiner Best Practices Analysis file.

type: '<fill in type here>'

# [Required] 
# The ID of the Catalog item.
# All registered versions for the same ID are shown together in the Catalog.
# This ID can not be changed. 
# If the ID is not filled in, the registration will fail with HTTP status code 500. 
# If the ID is filled in but does not exist yet, a new Catalog item will be registered with this ID.
# If the ID is filled in but does exist, properties of the item will be overwritten.
#   Must be a valid GUID.
id: '<fill in GUID here>'

# [Required] 
# The human-friendly name of the Catalog item. 
# Can be changed at any time.
#   Max length: 100 characters.
#   Cannot contain newlines.
#   Cannot contain leading or trailing whitespace characters.
title: '<fill in title here>'

# [Optional]
# General information about the Catalog item.
#   Max length: 100,000 characters
# Currently not shown in the Catalog UI but will be supported in the near future.
short_description: '<fill in description here>'

# [Optional]
# A valid URL that points to the source code.
#   A valid URL
#   Max length: 2048 characters
source_code_url: '<fill in source code url here>'

# [Optional]
# A valid URL that points to documentation.
#   A valid URL
#   Max length: 2048 characters
# Currently not shown in the Catalog UI but will be supported in the near future.
documentation_url: '<fill in documentation url here>'

# [Optional]
# People who are responsible for this Catalog item. Might be developers, but this is not required.
# Format: 'name <email> (url)'
#   The name is required; max 256 characters.
#   The email and url are optional, and should be in valid email/URL formats.
owners:
  - name: '<fill in name here>'
    email: '<fill in email here>'
    url: '<fill in url here>'

# [Optional]
# Tags that allow you to categorize your Catalog items.
#   Max number of tags: 5
#   Max length: 50 characters.
#   Cannot contain newlines.
#   Cannot contain leading or trailing whitespace characters.
tags:
  - '<fill in tag here>'

Registering a new version with the API

The register version API call allows you to create a new version for a Catalog item.

Note

A version can only be registered once. Registration will fail if you try to register an existing version number of a Catalog item.

Route parameter "catalogId" is the ID of the Catalog item of which a new version is registered, which is the same as the ID used to register the Catalog item. This must be a valid GUID.

To obtain this ID for an existing Catalog item, navigate to its details page in the Catalog. The ID is the last part of the URL.

API Definition

For a complete definition of the API, go to Key Catalog API Swagger.

This page also provides a quick way to execute the call: Expand the "catalog/{catalogId}/register/version" item, and click the Try it out button.

Important

Clicking the Try it out button will execute the register call on the production Catalog.

The Swagger.json can be used by e.g. Swagger CodeGen or AutoRest to generate client code.

HTTP method

POST

Body

The body of the request should be of type multipart/form-data and must contain the fields below.

file: <The Catalog item installation file>
versionNumber: <The version number you want to register>
versionDescription: <The description of the version you want to register>

Note

Supported types are a DataMiner protocol package (.dmprotocol) and a DataMiner application package (.dmapplication).
The version description must not exceed 1500 characters. The call will fail with a Bad Request error if the length exceeds the maximum allowed limit.
Versions following semantic version A.B.C.D will be displayed in an A.B.C range, versions following semantic version A.B.C will be displayed in an A range, and all other version formats will be displayed in the "Other" range.

Table of Contents

Registering a Catalog item

Important

Tip

Registering a Catalog item with workflows and tooling

Important

Registering a Catalog item with the API

API Definition

Important

HTTP method

Body

Tip

Note

Manifest file

Registering a new version with the API

Note

API Definition

Important

HTTP method

Body

Note