Dry-running Core v0.1.4-rc1 against an existing environment

[Donifez]

We run an on-prem lab from the shared environment on Core v0.1.3. Our last successful deployment used this retained overlay:

~/.hybridops/envs/shared/config/blueprints/onprem-authoritative-foundation.yml

It also has saved module state and run records under the same runtime root.

hyops update check now reports v0.1.4-rc1.

Before replacing the v0.1.3 installation, we need to know whether the existing overlay still loads and plans with the prerelease. This check must not deploy or change provider resources.

[jeleel-muibi]

Confirm how the environment is selected and whether the deployment uses the retained file with --file or a shipped blueprint with --ref. The upgrade check needs to exercise the same input that the next deployment will use.

[Donifez]

Our deployment command selects shared and uses --file with the retained overlay. It does not use --ref for this environment.

We have kept the v0.1.3 archive and checksum locally, along with a copy of the overlay and the last v0.1.3 plan output for comparison.

[jeleel-muibi]

The Core installation and the runtime root are separate. Installing v0.1.4-rc1 does not replace that overlay, saved module state, credentials, or old run records. That retention is not a compatibility guarantee. Check the overlay with an isolated v0.1.4-rc1 installation before changing the active Core install.

[Donifez]

We installed the v0.1.4-rc1 archive into a temporary HOME and prefix. The active v0.1.3 installation and shared runtime root were not touched.

check_home="$(mktemp -d)"
HOME="$check_home" ./install.sh
--prefix "$check_home/core"
--bin-dir "$check_home/bin"
--no-system-link
--no-setup-all

"$check_home/bin/hyops" blueprint validate
--file /path/to/onprem-authoritative-foundation-copy.yml
"$check_home/bin/hyops" blueprint plan
--file /path/to/onprem-authoritative-foundation-copy.yml

blueprint validate returned 0. The v0.1.4-rc1 plan loaded our copied overlay and produced the same step order as the v0.1.3 plan.

We also ran the candidate command with --ref onprem/authoritative-foundation@v1. That selected the blueprint shipped in v0.1.4-rc1, so the difference between our retained overlay and the release baseline was visible without touching the active environment.