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

Docs: Move from CloudCopy --> AzCopy #818

Closed
3 tasks done
SeanKilleen opened this issue Apr 8, 2015 · 8 comments
Closed
3 tasks done

Docs: Move from CloudCopy --> AzCopy #818

SeanKilleen opened this issue Apr 8, 2015 · 8 comments

Comments

@SeanKilleen
Copy link
Contributor

AzCopy is Microsoft's tool for copying files to Azure storage blog.

I think the Azure PowerShell tools unfortunately mostly support copying between blobs.

As of now, I recommend this instead of Azure PowerShell tools.

Build Server Changes

Code Changes

  • Understand current syntax of build process for copying items using AzCopy
  • Replace CloudCopy call with a command-line call to AzCopy

Testing

Not sure I can really help out with this one since it has to be done on the build server. I'll do my best to launch the command locally and at least ensure that it fails in an understandable way.

@Aaronontheweb
Copy link
Member

@SeanKilleen if we can make this work with a local copy of the AzCopy binary, per #819, then that'll make life a lot easier all around :p

@SeanKilleen
Copy link
Contributor Author

@Aaronontheweb 100% agreed, already put that into #819 for that exact reason. Wasn't thinking it through during my initial write-up.

@Aaronontheweb
Copy link
Member

Still have some bugs I need to sort out with AzCopy - setting right content-headers and such.

@SeanKilleen
Copy link
Contributor Author

@Aaronontheweb sorry that I don't have more visibility into what you're seeing. If you want to post a little more about it here (error messages, general background, etc.) I can try to do some legwork on it.

@Aaronontheweb
Copy link
Member

no error messages - just not seeing the results I expect inside Azure blob storage.

Saw two problems basically:

  1. Some content didn't look like it was being overwritten correctly (replacing an existing blob with a local file from source)
  2. Uploaded content had the incorrect MIME type

Just closed a PR that fixes problem 2 - going to see if the issue with problem 1 was related to something else I was doing last night.

@Aaronontheweb
Copy link
Member

@SeanKilleen turns out that the content not being overwritten correctly is an Azure CDN issue... I need to find a way to set a better default content-cache expiration header.

Might just disable the CDN for now and serve everything directly from blob storage.

@Aaronontheweb
Copy link
Member

But otherwise, everything else is working.

@Aaronontheweb
Copy link
Member

In order to use this with the CDN we'll need to be able to tell AzCopy to do this for each file: https://msdn.microsoft.com/en-us/library/gg680306.aspx

Not a big deal though. We'll just disable the CDN for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants