Rob Erez on 12 Feb, 2018 10:46 PM
As noted on the previous ticket this change was introduced to support packages that had invalid characters. For various reasons the blanket url encode felt like the safest way to solve the problem as we did not expect users to rely on specific naming of deployment folders. I will take a look at what we can do for valid semver characters which are over zealously getting encoded. In the meantime is it possible for you to rely on the Octopus.Action.Package.InstallationDirectoryPath variable to locate the deployed locations rather than assuming based on package Id? Cheers,
Rob Erez on 15 Feb, 2018 09:41 PM
s an update, a fix will be going out in the next release (2018.3.4) which will allow the + characters in the file paths. This may be an interim fix until we can implement a more robust solution to allow for future cases when we may have other feeds which have illegal characters and need to work against IIS.
Keep an eye out for this release in the next few days and let me know if you do (or don't) have any further problems.