feat: add update-variables commands for releases and runbook snapshots

[justin-newman]

Summary

• Adds octopus release update-variables — refreshes the variable snapshot on an existing release by POSTing to /api/{spaceId}/releases/{releaseId}/snapshot-variables
• Adds octopus runbook snapshot update-variables — refreshes the variable snapshot on an existing runbook snapshot (defaults to the published snapshot) by POSTing to /api/{spaceId}/runbookSnapshots/{id}/snapshot-variables

Both commands replace the need for manual PowerShell/REST calls to update variable snapshots, support interactive prompts and --no-prompt automation mode, and emit a deep link and automation command on success.

Usage

# Release
octopus release update-variables -p MyProject -v 1.2.3

# Runbook snapshot (published snapshot)
octopus runbook snapshot update-variables -p MyProject -r "Restart App"

# Runbook snapshot (specific snapshot)
octopus runbook snapshot update-variables -p MyProject -r "Restart App" --snapshot "Snapshot 40C9ENM"

Test plan

• octopus release update-variables -p <project> -v <version> against a real server — confirm variables refreshed in Octopus UI
• octopus runbook snapshot update-variables -p <project> -r <runbook> — confirm published snapshot variables refreshed
• octopus runbook snapshot update-variables -p <project> -r <runbook> --snapshot <name> — confirm named snapshot updated
• --no-prompt mode with all flags — no interactive prompts, no automation command printed
• Missing required flags in --no-prompt mode — clear error returned
• Runbook with no published snapshot and no --snapshot flag — error message guides user

[Copilot]

Pull request overview

Adds new CLI subcommands to refresh (“re-snapshot”) variables on existing Octopus releases and runbook snapshots by calling the Octopus Server snapshot-variables endpoints, reducing the need for manual REST/PowerShell steps.

Changes:

• Add octopus release update-variables to POST /api/{spaceId}/releases/{releaseId}/snapshot-variables.
• Add octopus runbook snapshot update-variables to POST /api/{spaceId}/runbookSnapshots/{snapshotId}/snapshot-variables (defaulting to the published snapshot).
• Wire both commands into their respective parent command groups.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
pkg/cmd/release/update_variables/update_variables.go	Implements release update-variables command, including interactive prompting and POST call to refresh the release variable snapshot.
pkg/cmd/release/release.go	Registers the new release update-variables subcommand.
pkg/cmd/runbook/snapshot/update_variables/update_variables.go	Implements runbook snapshot update-variables command, including snapshot resolution and POST call to refresh the runbook snapshot variable snapshot.
pkg/cmd/runbook/snapshot/snapshot.go	Registers the new runbook snapshot update-variables subcommand.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[hnrkndrssn]

Thanks @justin-newman for your contribution, I've left some comments for your attention.

[justin-newman]

Thanks for the review, @hnrkndrssn. Here's how I'm addressing the feedback:

1. Legacy releaseNumber alias: removed. Agreed it doesn't belong on a brand-new command.

2. / 3. snapshot-variables should live in the go client: done. I've added two additive package functions to go-octopusdeploy:

• releases.SnapshotVariables(client, spaceID, releaseID) maps to POST /releases/{id}/snapshot-variables
• runbooks.SnapshotVariables(client, spaceID, snapshotID) maps to POST /runbookSnapshots/{id}/snapshot-variables

Each follows the existing package conventions (validate, expand uritemplates, call newclient.Post), mirroring GetReleaseDeploymentTemplate and GetSnapshot respectively. Both CLI commands now delegate to these instead of hand-rolling http.NewRequest/DoRawRequest.

Client PR: OctopusDeploy/go-octopusdeploy#430

Ordering: this PR depends on #430. Once #430 merges and a version is tagged, I'll bump the go-octopusdeploy dependency here, drop the temporary local replace, and push the refactor commits, at which point this is ready for another look.

[justin-newman]

any follow-up on this @hnrkndrssn?

[hnrkndrssn]

any follow-up on this @hnrkndrssn?

Hey @justin-newman my sincere apologies, I've not been able to get back to this PR yet. I will make time for it today and get sure to get it reviewed and any feedback I have to you. 🙏

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Suppressed comments (1)

pkg/cmd/release/update_variables/update_variables.go:160

• When --project is provided in interactive mode, selectors.FindProject may return (nil, nil) if the project isn't found; the current code then passes a nil project into release selection. Also, shared.SelectRelease hardcodes "Progression" into the prompt text, which is confusing for an update-variables operation. Add a nil check and select from release versions with a task-appropriate prompt.

		selectedProject, err = selectors.FindProject(opts.Client, opts.Project.Value)
		if err != nil {
			return err
		}
	}

	if opts.Version.Value == "" {
		selectedRelease, err := shared.SelectRelease(opts.Client, selectedProject, opts.Ask, "Update Variables for")
		if err != nil {
			return err
		}
		opts.Version.Value = selectedRelease.Version
	}