From db4f4902e260e12985b6d8170d2c1c5397ba15e7 Mon Sep 17 00:00:00 2001 From: Sima Zhu Date: Thu, 6 Jun 2019 16:37:33 -0700 Subject: [PATCH 1/6] Readme for storage queue --- storage/client/README.md | 365 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 365 insertions(+) create mode 100644 storage/client/README.md diff --git a/storage/client/README.md b/storage/client/README.md new file mode 100644 index 0000000000000..dfa9428f54c54 --- /dev/null +++ b/storage/client/README.md @@ -0,0 +1,365 @@ +# Azure Storage Queue client library for Java +Azure Queue storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. +A single queue message can be up to 64 KB in size, and a queue can contain millions of messages, up to the total capacity limit of a storage account. + +[Source code][source_code] | [Package (Maven)][package] | [API reference documentation][api_documentation] | [Product documentation][storage_docs] + +## Getting started + +### Prerequisites + +- [Java Development Kit (JDK)][jdk] with version 8 or above +- [Azure Subscription][azure_subscription] +- [Create Strorage Account][storage_account] + +### Adding the package to your product + +```xml + + com.azure + azure-storage + 12.0.0 + +``` + +### Create a Storage Account +To create a Storage Account you can use the Azure Portal or [Azure CLI][azure_cli]. + +```Powershell +az group create \ + --name storage-resource-group \ + --location westus +``` + +### Authenticate the client + +In order to interact with the Storage service (Blob, Queue, Message, MessageId, File) you'll need to create an instance of the Service Client class. +To make this possible you'll need the Account SAS (shared access signature) string of Storage account. Learn more at [SAS Token] [sas_token] + +#### Get Credentials + +Use the [Azure CLI][azure_cli] snippet below to get the SAS token from the Storage account. + +```Powershell +az storage blob generate-sas + --account-name {storage account name} + --account-key {storage account key} + --container-name {name of blob container} + --name {blob name} + --permissions {permission to grant} + --expiry {date/time to expire SAS token} +``` + +```Powershell +#usage example +az storage blob generate-sas + --account-name azstoragesdkaccount + --account-key iseSbogGerMqZj17Xz77XPCPutCqdnDHVOx3ZZsc+UVWfqrrPZRP7bFv64aL8X1Fl06++3JNiuU0iQirr9VCqw== + --container-name javablobsettiererror15514606921543 + --name javablobsettiererror15514606921543 + --permissions rwdac + --expiry 2019-06-05 +``` +Alternatively, get the Account SAS Token from the Azure Portal. + +## Key concepts +### URL format +Queues are addressable using the following URL format: +https://.queue.core.windows.net/ +The following URL addresses a queue in the diagram: +https://myaccount.queue.core.windows.net/images-to-download + +#### Resource URI Syntax +For the storage account, the base URI for queue operations includes the name of the account only: +```$xslt +https://myaccount.queue.core.windows.net +``` +For a queue, the base URI includes the name of the account and the name of the queue: +```$xslt +https://myaccount.queue.core.windows.net/myqueue +``` + +Each resource may also have components, which are expressed as part of the query string on the base URI. The syntax for the query string is `?comp=`. +Currently, the following resource components are available for queue resources, as parameters on the URI. + +| Component | Supported resources | Description | +|:----------:|:-------------:|------| +| `list` | Account | Enumerates the entities beneath this resource. On the account, returns the list of queues. | +| `metadata` | Queue | Sets or returns queue properties, including user-defined metadata. | + +### Supported HTTP Operations +Each resource supports operations based on the HTTP verbs GET, PUT, HEAD, and DELETE. +The verb, syntax, and supported HTTP version(s) for each operation appears on the reference page for each operation. + +### Queue Names +Every queue within an account must have a unique name. The queue name must be a valid DNS name, and cannot be changed once created. Queue names must confirm to the following rules: +1. A queue name must start with a letter or number, and can only contain letters, numbers, and the dash (-) character. +1. The first and last letters in the queue name must be alphanumeric. The dash (-) character cannot be the first or last character. Consecutive dash characters are not permitted in the queue name. +1. All letters in a queue name must be lowercase. +1. A queue name must be from 3 through 63 characters long. + +### Metadata Names +Metadata for a queue resource is stored as name-value pairs. +Note that metadata names preserve the case with which they were created, but are case-insensitive when set or read. +If two or more metadata headers with the same name are submitted for a resource, the Queue service returns status code 400 (Bad Request). + +### Timeout +A call to a Queue service API can include a server timeout interval, specified in the timeout parameter of the request URI. If the server timeout interval elapses before the service has finished processing the request, the service returns an error. +The maximum timeout interval for Queue service operations is 30 seconds. The Queue service automatically reduces any timeouts larger than 30 seconds to the 30-second maximum. +The following example REST URI sets the timeout interval for the List Queues operation to 20 seconds: +```$xslt +GET https://myaccount.queue.core.windows.net?comp=list&timeout=20 +``` + +### Queue Services +The queue service do operations on the queues in the storage account and manage the queue properties. + +### Queue Service Client + +The client performs the interactions with the Queue service, create or delete a queue, getting and setting Queue properties, list queues in account, and get queue statistics. An asynchronous, `QueueServiceAsyncClient`, and synchronous, `QueueClient`, client exists in the SDK allowing for selection of a client based on an application's use case. +Once you have the value of the SASToken you can create the queue service client with `${accountName}`, `${sasToken}`. +```Java +String queueServiceURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceClient queueServiceClient = QueueServiceClient.builder().endpoint(queueURL).build(); + +QueueClient newQueueServiceClient = queueServiceClient.createQueue("myqueue"); +``` + +or + +```Java +String queueServiceAsyncURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceAsyncClient queueServiceAsyncClient = QueueServiceAsyncClient.builder().endpoint(queueServiceAsyncURL).build(); +queueServiceAsyncClient.createQueue("newAsyncQueue").subscribe( + result -> { + // do something when new queue created + }, + error -> { + // do something if something wrong happened + }, + () -> { + // completed, do something + }); +``` + +### Queue +Azure Queue storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. +A single queue message can be up to 64 KB in size, and a queue can contain millions of messages, up to the total capacity limit of a storage account. + +### QueueClient +Once you have the value of the SASToken you can create the queue service client with `${accountName}`, `${queueName}`, `${sasToken}`. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); +// metadata is map of key-value pair, timeout is client side timeout +QueueClient newQueueClient = queueClient.create(metadata, timeout); +``` + +or + +```Java +String queueAsyncURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueAsyncName, sasToken) +QueueAsyncClient queueAsyncClient = QueueAsyncClient.builder().endpoint(queueAsyncURL).build(); +queueAsyncClient.create(metadata, timeout).subscribe( + result -> { + // do something when new queue created + }, + error -> { + // do something if something wrong happened + }, + () -> { + // completed, do something + }); +``` + +## Examples + +The following sections provide several code snippets covering some of the most common Configuration Service tasks, including: +- [Create a Queue](#Create-a-queue) +- [Delete a queue](#Delete-a-queue) +- [List the queues in account](#List-queues-in-account) +- [Get propertiesin Queue account](#Get-properties-in-queue-account) +- [Set propertiesin Queue account](#Set-properties-in-queue-account) +- [Get statistcs of queue](#Get-queue-service-statistics) +- [Enqueue message into a queue](#Enqueue-message-into-a-queue) +- [Update message into a queue](#Update-message-into-a-queue) +- [Peek messages into a queue](#Peek-messages-into-a-queue) +- [Dequeue messages from a queue](#Dequeue-messages-from-a-queue) +- [Delete message from a queue](#Delete-message-from-a-queue) +- [Get a Queue properties](#Get-a-queue-properties) +- [Set/Update a Queue metadata](#Set-a-queue-metadata) +### Create a queue + +Create a queue in the Storage Account. Throws StorageErrorException If the queue fails to be created. + +```Java +String queueServiceURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceClient queueServiceClient = QueueServiceClient.builder().endpoint(queueURL).build(); + +QueueClient newQueueServiceClient = queueServiceClient.createQueue("myqueue"); +``` +### Delete a queue + +Delete a queue in the Storage Account. Throws StorageErrorException If the queue fails to be deleted. +```Java +String queueServiceURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceClient queueServiceClient = QueueServiceClient.builder().endpoint(queueURL).build(); + +QueueClient newQueueServiceClient = queueServiceClient.deleteQueue("myqueue"); +``` + +### List queues in account + +List all the queues in account. +```Java +String queueServiceURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceClient queueServiceClient = QueueServiceClient.builder().endpoint(queueURL).build(); +// @param marker: Starting point to list the queues +// @param options: Filter for queue selection +queueServiceClient.listQueuesSegment(marker, options).forEach{ + queueItem -> {//do something} +}; +``` + +### Get properties in queue account + +Get queue properties in account, including properties for Storage Analytics and CORS (Cross-Origin Resource Sharing) rules. +```Java +String queueServiceURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceClient queueServiceClient = QueueServiceClient.builder().endpoint(queueURL).build(); + +Response properties = queueServiceClient.getProperties(); +``` + +### Set properties in queue account + +Set queue properties in account, including properties for Storage Analytics and CORS (Cross-Origin Resource Sharing) rules. +```Java +String queueServiceURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceClient queueServiceClient = QueueServiceClient.builder().endpoint(queueURL).build(); + +StorageServiceProperties properties = new StorageServiceProperties() { + // logging: some logging; + // HourMetrics: some metrics + // MinuteMetrics: some metrics + // Cors: some cors +} + +queueServiceClient.setProperties(properties); +``` + +### Get queue service statistics +he `Get Queue Service Stats` operation retrieves statistics related to replication for the Queue service. +It is only available on the secondary location endpoint when read-access geo-redundant replication is enabled for the storage account. +```Java +String queueServiceURL = String.format("https://%s.queue.core.windows.net/%s", accountName, sasToken) +QueueServiceClient queueServiceClient = QueueServiceClient.builder().endpoint(queueURL).build(); + +Response queueStats = queueServiceClient.getStatistics(); +``` + +### Enqueue message into a queue +The operation adds a new message to the back of the message queue. A visibility timeout can also be specified to make the message invisible until the visibility timeout expires. +A message must be in a format that can be included in an XML request with UTF-8 encoding. The encoded message can be up to 64 KB in size for versions 2011-08-18 and newer, or 8 KB in size for previous versions. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); + +queueClient.enqueueMessage("myMessage"); +``` + +### Update messaged from a queue +The operation updates a message in the message queue. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); +// @param messageId Id of the message +// @param popReceipt Unique identifier that must match the message for it to be updated +// @param visibilityTimeout How long the message will be invisible in the queue in seconds +queueClient.updateMessage(messageId, "new message", popReceipt, visibilityTimeout); +``` + +### Peek messages from a queue +The operation retrieves one or more messages from the front of the queue. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); + +queueClient.peekMessages().forEach(message-> {print message.messageText();}); +``` + + +### Dequeue messages from a queue +The operation retrieves one or more messages from the front of the queue. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); + +queueClient.dequeueMessage("myMessage").forEach(message-> {print message.messageText();}); +``` + + +### Delete message from a queue +The operation retrieves one or more messages from the front of the queue. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); + +queueClient.deleteMessage(messageId, popReceipt); +``` + +### Get a queue properties +The operation retrieves user-defined metadata and queue properties on the specified queue. Metadata is associated with the queue as name-values pairs. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); + +Response properties = queueClient.getProperties(); +``` + +### Set a queue metadata +The operation sets user-defined metadata on the specified queue. Metadata is associated with the queue as name-value pairs. +```Java +String queueURL = String.format("https://%s.queue.core.windows.net/%s%s", accountName, queueName, sasToken); +QueueClient queueClient = QueueClient.builder().endpoint(queueURL).build(); + +Map metadata = new HashMap<>() {{ + put("key1", "val1"); + put("key2", "val2"); +}}; +queueClient.setMetadata(metadata); +``` + + +## Troubleshooting + +### General + +When you interact with queue using this Java client library, errors returned by the service correspond to the same HTTP status codes returned for [REST API][storage_rest] requests. For example, if you try to retrieve a queue that doesn't exist in your Storage Account, a `404` error is returned, indicating `Not Found`. + +## Next steps + +[Quickstart: Create a Java Spring app with App Configuration](https://docs.microsoft.com/en-us/azure/azure-app-configuration/quickstart-java-spring-app) + +## Contributing + +If you would like to become an active contributor to this project please follow the instructions provided in [Microsoft Azure Projects Contribution Guidelines](http://azure.github.io/guidelines.html). + +1. Fork it +2. Create your feature branch (`git checkout -b my-new-feature`) +3. Commit your changes (`git commit -am 'Add some feature'`) +4. Push to the branch (`git push origin my-new-feature`) +5. Create new Pull Request + + +[source_code]: to-be-continue +[package]: to-be-continue +[api_documentation]: https://docs.microsoft.com/en-us/rest/api/storageservices/queue-service-rest-api +[storage_docs]: https://docs.microsoft.com/en-us/azure/storage/queues/storage-queues-introduction +[jdk]: https://docs.microsoft.com/en-us/java/azure/java-supported-jdk-runtime?view=azure-java-stable +[maven]: https://maven.apache.org/ +[azure_subscription]: https://azure.microsoft.com/en-us/free/ +[storage_account]: https://docs.microsoft.com/en-us/azure/storage/common/storage-quickstart-create-account?tabs=azure-portal +[azure_cli]: https://docs.microsoft.com/cli/azure +[sas_token]: https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1 +[storage_rest]: https://docs.microsoft.com/en-us/rest/api/storageservices/queue-service-error-codes From 4622ac8f33075cdcbb3b3cb1deeab258c55407f7 Mon Sep 17 00:00:00 2001 From: Sima Zhu Date: Fri, 7 Jun 2019 09:09:04 -0700 Subject: [PATCH 2/6] Address comments --- storage/client/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/storage/client/README.md b/storage/client/README.md index dfa9428f54c54..3523135125331 100644 --- a/storage/client/README.md +++ b/storage/client/README.md @@ -34,7 +34,7 @@ az group create \ ### Authenticate the client In order to interact with the Storage service (Blob, Queue, Message, MessageId, File) you'll need to create an instance of the Service Client class. -To make this possible you'll need the Account SAS (shared access signature) string of Storage account. Learn more at [SAS Token] [sas_token] +To make this possible you'll need the Account SAS (shared access signature) string of Storage account. Learn more at [SAS Token][sas_token] #### Get Credentials @@ -333,7 +333,7 @@ queueClient.setMetadata(metadata); ## Troubleshooting -### General +## General When you interact with queue using this Java client library, errors returned by the service correspond to the same HTTP status codes returned for [REST API][storage_rest] requests. For example, if you try to retrieve a queue that doesn't exist in your Storage Account, a `404` error is returned, indicating `Not Found`. From 5175b8ca6584a93a593e56e268400fe47b3819be Mon Sep 17 00:00:00 2001 From: Sima Zhu Date: Fri, 7 Jun 2019 11:24:02 -0700 Subject: [PATCH 3/6] Addressed comments. --- storage/client/README.md | 55 +++++++++++++++++++--------------------- 1 file changed, 26 insertions(+), 29 deletions(-) diff --git a/storage/client/README.md b/storage/client/README.md index 3523135125331..f41c0de60853e 100644 --- a/storage/client/README.md +++ b/storage/client/README.md @@ -38,30 +38,42 @@ To make this possible you'll need the Account SAS (shared access signature) stri #### Get Credentials -Use the [Azure CLI][azure_cli] snippet below to get the SAS token from the Storage account. +- SAS Token + +a. Use the [Azure CLI][azure_cli] snippet below to get the SAS token from the Storage account. ```Powershell -az storage blob generate-sas - --account-name {storage account name} - --account-key {storage account key} - --container-name {name of blob container} - --name {blob name} - --permissions {permission to grant} +az storage queue generate-sas + --name {queue name} --expiry {date/time to expire SAS token} + --permission {permission to grant} + --connection-string {connection string of the storage account} ``` ```Powershell #usage example -az storage blob generate-sas - --account-name azstoragesdkaccount - --account-key iseSbogGerMqZj17Xz77XPCPutCqdnDHVOx3ZZsc+UVWfqrrPZRP7bFv64aL8X1Fl06++3JNiuU0iQirr9VCqw== - --container-name javablobsettiererror15514606921543 - --name javablobsettiererror15514606921543 - --permissions rwdac +az storage queue generate-sas + --name javasdksas --expiry 2019-06-05 + --permission rpau + --connection-string DefaultEndpointsProtocol=https;AccountName=azstoragesdkaccount;AccountKey=PhOFTkuqB09cmsy0aMgd+cJfp75xU3dgjRMKrWxHHx4pFvuFIMOSK/fhzGci6zxFGk4CkmgoXFO3s91S9m+ICw==;EndpointSuffix=core.windows.net +``` +b. Alternatively, get the Account SAS Token from the Azure Portal. +``` +Go to your storage account -> Shared access signature -> Click on Generate SAS and connection string (after setup) ``` -Alternatively, get the Account SAS Token from the Azure Portal. +- Shared Key Credential +a. Use account name and account key. Account name is your storage account name. +``` +// Here is where we get the key +Go to your storage account -> Access keys -> Key 1/ Key 2 -> Key +``` +b. Use the connection string +``` +// Here is where we get the key +Go to your storage account -> Access Keys -> Keys 1/ Key 2 -> Connection string +``` ## Key concepts ### URL format Queues are addressable using the following URL format: @@ -79,14 +91,6 @@ For a queue, the base URI includes the name of the account and the name of the q https://myaccount.queue.core.windows.net/myqueue ``` -Each resource may also have components, which are expressed as part of the query string on the base URI. The syntax for the query string is `?comp=`. -Currently, the following resource components are available for queue resources, as parameters on the URI. - -| Component | Supported resources | Description | -|:----------:|:-------------:|------| -| `list` | Account | Enumerates the entities beneath this resource. On the account, returns the list of queues. | -| `metadata` | Queue | Sets or returns queue properties, including user-defined metadata. | - ### Supported HTTP Operations Each resource supports operations based on the HTTP verbs GET, PUT, HEAD, and DELETE. The verb, syntax, and supported HTTP version(s) for each operation appears on the reference page for each operation. @@ -103,13 +107,6 @@ Metadata for a queue resource is stored as name-value pairs. Note that metadata names preserve the case with which they were created, but are case-insensitive when set or read. If two or more metadata headers with the same name are submitted for a resource, the Queue service returns status code 400 (Bad Request). -### Timeout -A call to a Queue service API can include a server timeout interval, specified in the timeout parameter of the request URI. If the server timeout interval elapses before the service has finished processing the request, the service returns an error. -The maximum timeout interval for Queue service operations is 30 seconds. The Queue service automatically reduces any timeouts larger than 30 seconds to the 30-second maximum. -The following example REST URI sets the timeout interval for the List Queues operation to 20 seconds: -```$xslt -GET https://myaccount.queue.core.windows.net?comp=list&timeout=20 -``` ### Queue Services The queue service do operations on the queues in the storage account and manage the queue properties. From fe50f065a571a44600c7cda146edd24125061a2f Mon Sep 17 00:00:00 2001 From: Sima Zhu Date: Fri, 7 Jun 2019 13:40:56 -0700 Subject: [PATCH 4/6] Removed the irrelavant part --- storage/client/README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/storage/client/README.md b/storage/client/README.md index f41c0de60853e..26779540ba285 100644 --- a/storage/client/README.md +++ b/storage/client/README.md @@ -91,10 +91,6 @@ For a queue, the base URI includes the name of the account and the name of the q https://myaccount.queue.core.windows.net/myqueue ``` -### Supported HTTP Operations -Each resource supports operations based on the HTTP verbs GET, PUT, HEAD, and DELETE. -The verb, syntax, and supported HTTP version(s) for each operation appears on the reference page for each operation. - ### Queue Names Every queue within an account must have a unique name. The queue name must be a valid DNS name, and cannot be changed once created. Queue names must confirm to the following rules: 1. A queue name must start with a letter or number, and can only contain letters, numbers, and the dash (-) character. From 0aadacdbe93686d0d46730e5432bb2ca55e38b35 Mon Sep 17 00:00:00 2001 From: Sima Zhu Date: Mon, 10 Jun 2019 17:07:44 -0700 Subject: [PATCH 5/6] Addressed the comments. Leave some todo field for handle exception and subsection of examples. --- storage/client/README.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/storage/client/README.md b/storage/client/README.md index 26779540ba285..12085fd6c6a8e 100644 --- a/storage/client/README.md +++ b/storage/client/README.md @@ -38,7 +38,7 @@ To make this possible you'll need the Account SAS (shared access signature) stri #### Get Credentials -- SAS Token +- **SAS Token** a. Use the [Azure CLI][azure_cli] snippet below to get the SAS token from the Storage account. @@ -63,7 +63,8 @@ b. Alternatively, get the Account SAS Token from the Azure Portal. Go to your storage account -> Shared access signature -> Click on Generate SAS and connection string (after setup) ``` -- Shared Key Credential +- **Shared Key Credential** + a. Use account name and account key. Account name is your storage account name. ``` // Here is where we get the key @@ -91,6 +92,12 @@ For a queue, the base URI includes the name of the account and the name of the q https://myaccount.queue.core.windows.net/myqueue ``` +### Handling Exceptions + +```java +TODO +``` + ### Queue Names Every queue within an account must have a unique name. The queue name must be a valid DNS name, and cannot be changed once created. Queue names must confirm to the following rules: 1. A queue name must start with a letter or number, and can only contain letters, numbers, and the dash (-) character. @@ -98,12 +105,6 @@ Every queue within an account must have a unique name. The queue name must be a 1. All letters in a queue name must be lowercase. 1. A queue name must be from 3 through 63 characters long. -### Metadata Names -Metadata for a queue resource is stored as name-value pairs. -Note that metadata names preserve the case with which they were created, but are case-insensitive when set or read. -If two or more metadata headers with the same name are submitted for a resource, the Queue service returns status code 400 (Bad Request). - - ### Queue Services The queue service do operations on the queues in the storage account and manage the queue properties. From 474de5df536f7afa158f72dd0693865ee45641c4 Mon Sep 17 00:00:00 2001 From: Sima Zhu Date: Wed, 12 Jun 2019 11:13:18 -0700 Subject: [PATCH 6/6] no secret on readme --- storage/client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/storage/client/README.md b/storage/client/README.md index 12085fd6c6a8e..0537a4eb06adb 100644 --- a/storage/client/README.md +++ b/storage/client/README.md @@ -56,7 +56,7 @@ az storage queue generate-sas --name javasdksas --expiry 2019-06-05 --permission rpau - --connection-string DefaultEndpointsProtocol=https;AccountName=azstoragesdkaccount;AccountKey=PhOFTkuqB09cmsy0aMgd+cJfp75xU3dgjRMKrWxHHx4pFvuFIMOSK/fhzGci6zxFGk4CkmgoXFO3s91S9m+ICw==;EndpointSuffix=core.windows.net + --connection-string {connection string} ``` b. Alternatively, get the Account SAS Token from the Azure Portal. ```