Inconsistency with Azure Storage Cmdlets

[azure]

Inconsistency with Azure Storage Cmdlets

[matt1883]

We have Set/Get..Content as well. These cmdlets deal with string/byte appends and gets.

Set/Get..Content appends/gets content (bytes) to/from a file.
Import/Export.. uploads/downloads a file.

We chose to mirror the cmdlets in native PowerShell (Get-/Set-Content), which operate just like our cmdlets. We also have Import-/Export- for upload/download.

If folks would rather just have Set-/Get-...Content with a separate parameter set to handle file paths instead of bytes, we could make that change, and it may simplify the experience.

Thoughts?

[mwinkle]

Do we think a lot of folks will be using the powersehll command lets for byte/string appends? My assumption would be teh bulk of the scripted scenarios will be about files. I was surprised that it was import, coming from my experience with storage.

[matt1883]

Adding @begoldsm .

Good point. As you mentioned offline, Import/Export sounds very different from Azure Storage's Set/Get.

We'll add the file upload/download functionality of Import/Export into the existing Set/Get cmdlets to give a friendlier experience to those transitioning from Azure Storage. This would be added as a new file path parameter set.

[matt1883]

To answer your question, though: Yes, we had multiple customer requests to support appending bytes to a file without having to download and re-upload the file.