The SAS Viya Orders CLI, the command-line tool for managing SAS Viya software order assets, has recently introduced a new feature that enhances control and precision when downloading deployment assets. As of the latest version (1.7.0, released February 2025) available from the GitHub repository, users can now specify a cadence release value when downloading deployment assets. This addition addresses a use case you may have encountered when deploying or updating your software. Let’s check out how it works and why it matters.
The Problem: Hidden Patches in the Same Version Number
Imagine this scenario: On March 27th, a new SAS Viya version is released. You download the deployment assets and deploy them to a test environment. After running your tests, everything looks good, and you greenlight the deployment to production on March 30th.
Between March 27th and March 30th, SAS releases several patches for that version. The version number remains unchanged, and on the surface, there’s no obvious indication that the assets have been updated to include those new patches. You download the artifacts again on March 30th, expecting the same package you tested, only to find that the patched version is different. This discrepancy might go unnoticed until the production system behaves in an unexpected manner or generates some form of error.
The Solution: Specifying cadence release in the CLI
The new feature in the SAS Viya Orders CLI allows users to explicitly specify a cadence release, which denotes the 'patch version', when downloading deployment assets. This means you’re no longer constrained to downloading the latest patched version of SAS Viya, which was previously the default behaviour. Instead, you can pinpoint the exact release you want, matching what you tested, and avoid surprises in production.
This functionality mirrors capabilities in the SAS Viya Deployment Operator and sas-orchestration tool, where users can define a specific cadence release to ensure consistency across environments. By bringing this precision to the SAS Viya Orders CLI, SAS empowers users to maintain control over their deployment process, aligning with real-world needs where testing and production must stay in sync.
How It Works
The updated CLI now includes an option to specify the cadence release alongside the cadence name and version when using the deploymentAssets command. The exact syntax might look something like this (check the latest README.md for confirmation):
viya4-orders-cli deploymentAssets /
<order-number> /
<cadence-name> /
<version-number> /
<cadence-release-number>
Here’s a breakdown:
- <order-number> : Your specific SAS Viya order number.
- <cadence-name>: The release cadence (e.g., Stable, LTS).
- <cadence-version>: The version number (e.g., 2025.03).
- <cadence-release-number>: The new value that identifies the exact patch level or release ID you want.
For example, if you tested 2025.03 with a cadence release of 20250327*, you could ensure you download that exact artifact for production, even if patches have since incremented the release to, say, 20250330.
* Simplified example only; actual release numbers have an epoch date-time value like 20250326.1721414421837.
Why This Matters
This new feature tackles several key challenges:
- You can now guarantee that what you tested is what you deploy, avoiding the risk of untested patches appearing in production environments.
- No more guessing whether a release has been patched. You decide which artifact to pull based on your needs.
- For organisations with strict compliance requirements, this ensures you can track and replicate/automate the exact software state across deployments.
- You can still get the latest patch version by leaving cadence release unspecified.
This level of control eliminates the disconnect between testing and deployment, making the process smoother and more predictable.
Final Thoughts
The addition of the cadence release option in the SAS Viya Orders CLI is a useful feature for anyone managing SAS Viya deployments. It addresses a real-world need, balancing the need to stay up-to-date with software patches with the stability required for production environments.
Find more articles from SAS Global Enablement and Learning here.
