You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Updating F# doc to the new SDKs.
* Update F# docs with the new SDKs in file-storage
* Sort the namespace
* some code changes
Co-authored-by: Wenjie Yu <v-wenjyu@microsoft.com>
You'll need an Azure Storage connection string for this tutorial. For more information about connection strings, see [Configure Storage Connection Strings](/azure/storage/storage-configure-connection-string).
34
34
35
35
For the tutorial, you'll enter your connection string in your script, like this:
However, this is **not recommended** for real projects. Your storage account key is similar to the root password for your storage account. Always be careful to protect your storage account key. Avoid distributing it to other users, hard-coding it, or saving it in a plain-text file that is accessible to others. You can regenerate your key using the Azure portal if you believe it may have been compromised.
40
40
41
41
For real applications, the best way to maintain your storage connection string is in a configuration file. To fetch the connection string from a configuration file, you can do this:
The example below shows how to check the current usage for a share and how to set the quota for the share.`FetchAttributes` must be called to populate a share's `Properties`, and `SetProperties` to propagate local changes to Azure File Storage.
81
+
The example below shows how to check the current usage for a share and how to set the quota for the share.
### Generate a shared access signature for a file or file share
94
86
95
-
You can generate a shared access signature (SAS) for a file share or for an individual file. You can also create a shared access policy on a file share to manage shared access signatures. Creating a shared access policy is recommended, as it provides a means of revoking the SAS if it should be compromised.
87
+
You can generate a shared access signature (SAS) for a file share or for an individual file. You can also create a shared access policy on a file share to manage shared access signatures. Creating a shared access permissions is recommended, as it provides a means of revoking the SAS if it should be compromised.
96
88
97
-
Here, you create a shared access policy on a share, and then use that policy to provide the constraints for a SAS on a file in the share.
89
+
Here, you create a shared access permissions on a share, and then set that permissions to provide the constraints for a SAS on a file in the share.
For more information about creating and using shared access signatures, see [Using Shared Access Signatures (SAS)](/azure/storage/storage-dotnet-shared-access-signature-part-1) and [Create and use a SAS with Blob storage](/azure/storage/storage-dotnet-shared-access-signature-part-2).
102
94
@@ -108,13 +100,13 @@ You can copy a file to another file or to a blob, or a blob to a file. If you ar
108
100
109
101
Here, you copy a file to another file in the same share. Because this copy operation copies between files in the same storage account, you can use Shared Key authentication to perform the copy.
Here, you create a file and copy it to a blob within the same storage account. You create a SAS for the source file, which the service uses to authenticate access to the source file during the copy operation.
You can copy a blob to a file in the same way. If the source object is a blob, then create a SAS to authenticate access to that blob during the copy operation.
120
112
@@ -124,7 +116,7 @@ Azure Storage Analytics supports metrics for File storage. With metrics data, yo
124
116
125
117
You can enable metrics for File storage from the [Azure portal](https://portal.azure.com), or you can do it from F# like this:
0 commit comments