SAS Mirror Manager: Downloading Specific Releases

The Problem

While using SAS Mirror Manager to download software assets, I noticed that despite specifying a deployment assets file (using `--deployment-assets`), the tool was consistently downloading the latest release instead of the release specified in the provided file. Initially, it was unclear if this was a bug, a misunderstanding of the documentation, or if I was verifying the downloaded release incorrectly.

Investigation

After careful examination of the documentation and troubleshooting steps, the core issue was identified: * **Default Behavior:** By default, if no specific release is specified, SAS Mirror Manager defaults to pulling the most recent release available. This default behavior explained why the deployment assets file's release information was seemingly ignored. The tool needs an explicit instruction to prioritize the assets file's release.

The Solution

The solution lies in using the `--release` option within the `mirrormgr` command. This option allows for explicit specification of the desired release, overriding the default behavior. Here's an example of how to effectively use the `--release` option:

cadencerelease=$(grep -E 'Cadence.Release' sas-bases/checksums.txt | awk '{print $NF}')
...
mirrormgr mirror registry \
--destination "$mirror" \
--deployment-data "SASViyaV4_${order}_certs.zip" \
--username "$mirroruser" \
--password "$mirrorpass" \
--cadence "${cadence}-${version}" \
--release "${cadencerelease}" \
--workers 10

In this example: * **`cadencerelease`**: This variable is dynamically populated with the cadence and release information extracted from your `checksums.txt` file. * **`--release "${cadencerelease}"`**: This crucial part instructs Mirror Manager to use the release defined in the `cadencerelease` variable.

Additional Tips

* **Verification:** To confirm the downloaded release, navigate to your repository path under `sas-bases/lod/<cadence>/<version>/` The directories within this path should correspond to the releases you've downloaded. * **Multiple Releases & Cadences:** Mirror Manager allows you to download different releases of the same cadence or even different cadences to the same download location. This provides flexibility in managing your SAS software assets.

Conclusion

Using the `--release` option with SAS Mirror Manager is essential for precise control over the downloaded release. Understanding the tool's default behavior and utilizing this option ensures that you are working with the intended software version, avoiding potential compatibility issues or unexpected updates.