Table of Contents

Registering a new version of a connector in the Catalog using a GitHub Action

This tutorial demonstrates how to add a new version to a Catalog item using the Catalog API and GitHub Actions. In the tutorial, you will register your own version of an example connector. The tutorial builds on the example from the tutorial Registering a new connector in the Catalog, so unless you already know how to register a new Catalog item and have done so already, we recommend that you follow that tutorial first.

While this tutorial uses the example of a connector, registering a new version for a different type of Catalog item is very similar.

Expected duration: 10 minutes

Note

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.

Prerequisites

Overview

Step 1: Create the GitHub Actions Workflow file

  1. On your GitHub page, go to the Actions tab and select set up workflow yourself.

  2. Paste the pipeline template below into this file.

    Important

    Make sure to change the CATALOG_ID environment variable to the Catalog ID of the item for which you will register a new version. If you followed the tutorial Registering a new connector in the Catalog, this is the ID that was returned in the last step. If you are registering a new version for a different Catalog item, you can find it by navigating to its details page in the Catalog and checking the last part of the URL.


name: Build and Register a Catalog version

on:
  push:
    branches:
      - main
  workflow_dispatch:  # Add this line to enable manual triggering

jobs:
  build_and_upload:
    runs-on: ubuntu-latest

    steps:
      # Checkout the repository
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Use GitHub run number for versioning
        run: echo "VERSION=1.0.0.${{ github.run_number }}" >> $GITHUB_ENV

      - name: Use GitHub environment variable to store Catalog ID
        run: echo "CATALOG_ID=1742495c-9231-4eeb-a56e-1fec8189246e" >> $GITHUB_ENV

      # Install the Skyline DataMiner Tooling
      - name: Install .NET Tools
        run: |
          dotnet tool install -g Skyline.DataMiner.CICD.Tools.Packager              
          dotnet tool install -g Skyline.DataMiner.CICD.Tools.CatalogUpload

      # Create the DataMiner Protocol package
      - name: Create DataMiner Protocol Package
        run: dataminer-package-create dmprotocol "${{ github.workspace }}" --name catalog_registration_tutorial --output "${{ github.workspace }}/Packages"

      # Upload the DataMiner Protocol package
      - name: Upload DataMiner Protocol Package to Catalog
        id: upload_to_catalog
        shell: bash
        run: |
          dataminer-catalog-upload with-registration \
            --path-to-artifact "${{ github.workspace }}/Packages/catalog_registration_tutorial.dmprotocol" \
            --artifact-version "${{ env.VERSION }}" \
            --dm-catalog-token "${{ secrets.API_TOKEN }}" \
            --catalog-identifier "${{ env.CATALOG_ID }}"

Step 2: Add a GitHub secret

To securely store sensitive information like the API token, you will need to add a GitHub secret:

  1. Create an organization key token to authenticate the register version call from the Catalog API:

    1. In the Admin app, under Organization in the sidebar on the left, select the Keys page.

    2. At the top of the page, click New Key.

    3. Configure the key with a label of your choice and the permission Register catalog items.

      Organization Key

    4. Copy the key so you can use it later.

    Important

    You need to have the Owner role in order to access/create organization keys. See Changing the role of a dataminer.services user for information on how to change a role for a user.

  2. In your GitHub repository, go to the Settings page.

  3. In the sidebar on the left, select Secrets and variables > Actions, and then click the New repository secret button.

    New repository secret button

  4. Specify the name API_TOKEN, and add the organization key you copied earlier as the value.

Note

In case using an organization key results in issues, you can try using a system key instead.

Step 3: Push the workflow file

Commit and push the addition of the dataminer-catalog-pipeline.yml file in the .github/workflows folder to your repository. You can use the following commands for this:

git add .github/workflows/dataminer-catalog-pipeline.yml
git commit -m "Add GitHub Actions pipeline for catalog version registration"
git push origin main

Step 4: Trigger the workflow

To create a new version, push a change to the main branch of the repository (or the branch you have defined in the workflow under the on section). The GitHub Actions pipeline will automatically be triggered.

You can also manually trigger the workflow by navigating to the Actions tab in your repository, selecting the pipeline, and then clicking Run workflow.

Step 5: Monitor workflow execution

  1. Go to the Actions tab of your GitHub repository.

    You should see the pipeline you created listed there.

  2. Select the workflow to see its progress.

    You can view detailed logs for each step to check for errors or success messages.

  3. When the workflow has run successfully, navigate to the item in the DataMiner Catalog.

    You will be able to see the registered version in the versions tab.

Propose changes