michelle-luana
commented
1 week ago The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future.
We prioritize issues based on the number of people affected, the impact type, and available workarounds.
If you’ve encountered this issue and haven’t informed our support team, please email support@octopus.com. Knowing how many people this issue affects helps us determine its priority.
Severity
Sev-3-Low
Version
2023.1 (Note this is an old issue that didn't have a corresponding Github issue)
What happened?
When trying to populate a prompted variable from the Azure Dev Ops pipeline task "Deploy Octopus Release" if you have a colon in the value you wish to populate it does not push the full value to Octopus.
Reproduction
Deployment requires a prompted variable that is a string. Customer needs a URL passing through. They put "https://website.com/" in the "Values for prompted variables" on the "Deploy Ocotpus Release" task. When that value is then read in Octopus only "https" remains.
More Information
Internal link
Workaround
To note, this functionality works fine the OctoCLI. (e.g. "--variable Prompted:https://urltest/" populates the full URL value into Octopus).