Package ID's with / characters are mishandled by the CLI

[borland]

[re-worded from customer support incident]

GitHub packages puts a / character inside the package ID/name string.

For example, something like "OctopusDeploy/utils" would be a complete atomic package ID

Attempting to create a release, and reference this package so you can change it's version results in a CLI command like this:

--package='OctopusDeploy/utils:0.2.5-dev.fix.3'

The CLI internally uses not only : but also / and = as delimeters, so this command line argument is treated as

--package='OctopusDeploy:utils:0.2.5-dev.fix.3'

Expectation:

Match a package with ID OctopusDeploy/utils.

Behaviour:

Match a package with ID OctopusDeploy, package reference name utils

This doesn't match any packages, so the command line argument appears to be ignored.

Workaround

The octopus server allows / in package ID's, but does not allow them in package reference names, so you can use the alternate syntax to select via the package reference name directly.

Package:
ID: OctopusDeploy/utils
Reference: OctopusDeploy-utils

command line

--package='*:OctopusDeploy-utils:0.2.5-dev.fix.3'