Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New-OctopusArtifact doesn't encode the name parameter #1889

Closed
Damovisa opened this issue Aug 13, 2015 · 2 comments
Closed

New-OctopusArtifact doesn't encode the name parameter #1889

Damovisa opened this issue Aug 13, 2015 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@Damovisa
Copy link

It looks like if you leave out the -name param, we Base64-encode the filename, however if you include it, we don't.

Source: https://secure.helpscout.net/conversation/111862907/812/

@Damovisa Damovisa added kind/bug This issue represents a verified problem we are committed to solving in progress labels Aug 13, 2015
@Damovisa Damovisa self-assigned this Aug 13, 2015
@octoreleasebot
Copy link

Release note: New-OctopusArtifact now encodes the name parameter correctly

@Damovisa Damovisa added this to the 3.0.14 milestone Aug 13, 2015
@michaelnoonan michaelnoonan modified the milestones: 3.0.14, 3.0.15 Aug 17, 2015
@lock
Copy link

lock bot commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants