At Skyline, we're always working to improve the security, flexibility, and efficiency of our DataMiner deployment tooling. As part of these efforts, we are announcing important changes to two widely used tools: the Skyline DataMiner Deploy Action (GitHub Action) and Skyline.DataMiner.CICD.Tools.DataMinerDeploy (.NET Tool). These updates are essential for enhancing security and providing greater flexibility in your CI/CD workflows.
Who is affected?
If you’re a CI/CD developer or a DevOps engineer using either of the following tools, these changes apply to you:
- Skyline DataMiner Deploy Action (GitHub)
- Skyline.DataMiner.CICD.Tools.DataMinerDeploy (.NET)
What's changing?
Starting May 1, 2025, several significant updates will take place. Here’s what you need to know:
Skyline DataMiner Deploy Action (GitHub)
The first major change is that the artifact-id input will be deprecated. Going forward, deployments will rely on the catalog-guid defined within the existing manifest.yml file.
Additionally, the api-key input must now exclusively contain an Organization Key, which provides better security and more control over deployment permissions. A new mandatory input, agent-destination-id, will also be required to explicitly specify the target DataMiner Agent.
The old command:
- name: Skyline DataMiner Deploy-Deploy Action Windows OLD
uses: SkylineCommunications/Skyline-DataMiner-Deploy-Action@prepareForDeployDeprecation
with:
stage: Deploy
github-token: ${{ secrets.GITHUB_TOKEN }}
api-key: ${{ secrets.DATAMINER_DEPLOY_KEY }}
artifact-id: ${{ steps.upload.outputs.artifact-id }}
Red = deprecated; Green = changed; Blue = new
The new required command:
- name: Skyline DataMiner Deploy-Deploy Action Windows NEW
uses: SkylineCommunications/Skyline-DataMiner-Deploy-Action@prepareForDeployDeprecation
with:
stage: Deploy
github-token: ${{ secrets.GITHUB_TOKEN }}
api-key: ${{ secrets.DATAMINER_TOKEN }}
version: "${{ github.ref_name }}"
agent-destination-id: 3da53c6f-7717-4a14-b6ab-c71acb376a8a
These changes will make your deployment process more secure and streamlined by using Organization Keys and specific DataMiner destination GUIDs. This not only enhances security but also ensures better management of deployment permissions and clearer separation of deployment targets.
Skyline.DataMiner.CICD.Tools.DataMinerDeploy (.NET)
If you’re using the .NET tool, the key change is the way deployments from the Catalog will be handled. Starting May 1, 2025, the tool will no longer accept the artifact-id obtained from the upload result. Instead, you'll deploy using catalog-id, catalog-version, and agent-destination-id as stable identifiers.
The old command:
dataminer-package-deploy from-catalog --artifact-id {upload result} --dm-catalog-token "dmSystemToken"Red = deprecated; Green = changed; Blue = new
The new required commands:
dataminer-package-deploy from-catalog --catalog-id {catalog guid} --catalog-version {catalog version} --agent-destination-id {agent guid} --dm-catalog-token "organizationToken"These updates ensure compatibility with the latest Skyline.DataMiner.Sdk projects and workflows, which no longer rely on return values from previous upload tools. By transitioning to stable catalog-based identifiers, your CI/CD processes become more reliable, predictable, and secure.
For volatile packages, nothing has changed. As shown in the code example below, volatile uploads still use the artifact-id and dm-system-token just like before.
dataminer-package-deploy from-volatile --artifact-id "dmscript/00000000-0000-0000-0000-000000000000" --dm-system-token "agentToken"What's next?
You will start receiving clear warning messages in your pipeline logs immediately, alerting you to the use of deprecated methods. On May 1, 2025, these deprecated methods will be removed, and workflows that have not been updated by this date will fail.
So, what should you do now? To keep your CI/CD pipelines running smoothly, we recommend taking the following actions:
- Replace any deprecated parameters with the new required ones.
- Use an Organization Key. You can generate one in your organization’s admin portal at admin.dataminer.services.
- Identify the correct agent-destination-id. You’ll find this in the URL of your DataMiner System in the Admin app (it’s the last GUID in the address).
By making these updates now, you’ll make sure your CI/CD workflows remain secure, reliable, and future-proof. We understand changes like these impact your processes, and we're here to support you through this transition.
We appreciate you taking the time to update, as it helps keep deployments running smoothly and securely. 🚀