Table of Contents

GitHub secrets and tokens

Several tools, starter workflows, and reusable workflows provided by Skyline will require secrets and tokens to run correctly. Below, you can find information on where to find the tokens you may need and how to add them as a secret in your repository.

Public vs. private repositories

If you use a paid GitHub License or a public repository, it is possible that some secrets and tokens have been set as organization secrets, in which case you can use those.

Otherwise, you will have to "override" the organization secrets by adding repository secrets.

Adding a key as a secret in the repository

A key should be added as a secret in the repository, so that it is stored securely in GitHub and not in source control.

  1. Copy the value from the required key.

  2. In your GitHub repository, go to Settings.

  3. In the pane on the left, under Security, select Secrets > Actions.

    Actions page

  4. In the top-right corner, click New repository secret.

  5. Specify a name for your secret (e.g. DATAMINER_DEPLOY_KEY), paste the key as the value for the secret, and then save the secret.

    Once it is saved, your secret will be displayed in the repository secrets, and you will be able to use it in a workflow.

Note

For more information about secrets, refer to the GitHub Documentation.

SONAR_TOKEN SonarCloud key

Several provided workflows may require static code analysis through SonarCloud in order to meet quality standards. To perform such analysis, access is needed to a SonarCloud project.

  • Name: SONAR_TOKEN
  • Value: The value of the secret is an API token that can be created in SonarCloud under the Security tab of the account settings.

DATAMINER_DEPLOY_KEY dataminer.services system key

A dataminer.services system key is scoped to the specific DMS for which it was created and can only be used for deployments to that DMS. It can also be used to upload private artifacts to the DataMiner Catalog that will only be accessible for the organization that your DMS belongs to.

dataminer.services organization key

A dataminer.services organization key is scoped to the specific organization for which it was created and can only be used to perform uploads to the DataMiner Catalog. This includes uploading private artifacts to the DataMiner Catalog that will only be accessible for the organization that your DMS belongs to.

For more information on how to create a dataminer.services key, see Managing dataminer.services keys.

Propose changes