@azure/storage-queue

Azure Queue storage provides cloud messaging between application components. In designing applications for scale, application components are often decoupled, so that they can scale independently. Queue storage delivers asynchronous messaging for communication between application components, whether they are running in the cloud, on the desktop, on an on-premises server, or on a mobile device. Queue storage also supports managing asynchronous tasks and building process work flows.

This project provides a client library in JavaScript that makes it easy to consume Microsoft Azure Queue Storage service.

Version: 12.0.0-preview.5

• Queue Storage
  • Get/Set Queue Service Properties
  • Create/List/Delete Queues
  • Enqueue/Dequeue/Peek/Clear/Update/Delete Queue Messages
• Features new
  • Asynchronous I/O for all operations using the async methods
  • HttpPipeline which enables a high degree of per-request configurability
  • 1-to-1 correlation with the Storage REST API for clarity and simplicity

This library is compatible with Node.js and browsers, and validated against LTS Node.js versions (>=8.16.0) and latest versions of Chrome, Firefox and Edge.

You need polyfills to make this library work with IE11. The easiest way is to use @babel/polyfill, or polyfill service.

You can also load separate polyfills for missed ES feature(s).This library depends on following ES features which need external polyfills loaded.

• Promise
• String.prototype.startsWith
• String.prototype.endsWith
• String.prototype.repeat
• String.prototype.includes
• Array.prototype.includes
• Object.assign
• Object.keys (Override IE11's Object.keys with ES6 polyfill forcely to enable ES6 behavior)
• Symbol

There are differences between Node.js and browsers runtime. When getting started with this library, pay attention to APIs or classes marked with "ONLY AVAILABLE IN NODE.JS RUNTIME" or "ONLY AVAILABLE IN BROWSERS".

• Shared Key Authorization based on account name and account key
  • SharedKeyCredential
• Shared Access Signature(SAS) generation
  • generateAccountSASQueryParameters()
  • generateQueueSASQueryParameters()

The preferred way to install the Azure Queue Storage client library for JavaScript is to use the npm package manager. Simply type the following into a terminal window:

npm install @azure/storage-queue@12.0.0-preview.5

In your TypeScript or JavaScript file, import via following:

import * as AzureStorageQueue from "@azure/storage-queue";

Or

const AzureStorageQueue = require("@azure/storage-queue");

To use the library with JS bundle in the browsers, simply add a script tag to your HTML pages pointing to the downloaded JS bundle file(s):

<script src="https://mydomain/azure-storage-queue.min.js"></script>

The JS bundled file is compatible with UMD standard, if no module system found, following global variable(s) will be exported:

Download latest released JS bundles from links in the GitHub release page.

You need to set up Cross-Origin Resource Sharing (CORS) rules for your storage account if you need to develop for browsers. Go to Azure portal and Azure Storage Explorer, find your storage account, create new CORS rules for blob/queue/file/table service(s).

For example, you can create following CORS settings for debugging. But please customize the settings carefully according to your requirements in production environment.

• Allowed origins: *
• Allowed verbs: DELETE,GET,HEAD,MERGE,POST,OPTIONS,PUT
• Allowed headers: *
• Exposed headers: *
• Maximum age (seconds): 86400

You can use the const Azure = require("@azure/storage-queue"); shown above then use types and functions from Azure.Or you can selectively import certain types,

const { QueueServiceClient, SharedKeyCredential } = require("@azure/storage-queue"); );

Use the constructor to create an instance of QueueServiceClient, passing in the credential, and options to configure the HTTP pipeline (optional).

 const account = "<account>"; const accountKey = "<accountkey>"; const sharedKeyCredential = new SharedKeyCredential(account, accountKey); const queueServiceClient = new QueueServiceClient( `https://${account}.queue.core.windows.net`, sharedKeyCredential, { retryOptions: { maxTries: 4 }, telemetry: { value: "BasicSample/V11.0.0" } } );

Use QueueServiceClient.listQueues() function to iterate the queues,with the new for-await-of syntax:

let iter1 = queueServiceClient.listQueues(); let i = 1; for await (const item of iter1) { console.log(`Queue${i}: ${item.name}`); i++; }

Alternatively without for-await-of:

let iter2 = await queueServiceClient.listQueues(); let i = 1; let item = await iter2.next(); while (!item.done) { console.log(`Queue ${i++}: ${item.value.name}`); item = await iter2.next(); }

For a complete sample on iterating queues please see samples/typescript/iterators.ts.

Use QueueServiceClient.getQueueClient() function to create a new queue.

const queueName = `newqueue${new Date().getTime()}`; const queueClient = queueServiceClient.getQueueClient(queueName); const createQueueResponse = await queueClient.create(); console.log( `Create queue ${queueName} successfully, service assigned request Id: ${createQueueResponse.requestId}` );

Use sendMessage() to add a message to the queue:

 const sendMessageResponse = await queueClient.sendMessage("Hello World!"); console.log( `Sent message successfully, service assigned message Id: ${sendMessageResponse.messageId}, service assigned request Id: ${sendMessageResponse.requestId}` );

QueueClient.peekMessages() allows looking at one or more messages in front of the queue. This calldoesn't prevent other code from accessing peeked messages.

const peekMessagesResponse = await queueClient.peekMessages(); console.log(`The peeked message is: ${peekMessagesResponse.peekedMessageItems[0].messageText}`);

Messages are processed in two steps.

• First call queueClient.receiveMessages(). This makes the messages invisible to other code reading messagse from this queue for a default period of 30 seconds.
• When processing of a message is done, call queueClient.deleteMessage() with the message's popReceipt.

If your code fails to process a message due to hardware or software failure, this two-step process ensures that another instance of your code can get the same message and try again.

const response = await queueClient.receiveMessages(); if (response.receivedMessageItems.length == 1) { const receivedMessageItem = response.receivedMessageItems[0]; console.log(`Processing & deleting message with content: ${receivedMessageItem.messageText}`); const deleteMessageResponse = await queueClient.deleteMessage(receivedMessageItem.messageId, receivedMessageItem.popReceipt); console.log( `Delete message succesfully, service assigned request Id: ${deleteMessageResponse.requestId}` ); }

const deleteQueueResponse = await queueClient.delete(); console.log( `Delete queue successfully, service assigned request Id: ${deleteQueueResponse.requestId}` );

A complete example of basic scenarios is at samples/basic.ts.

It could help diagnozing issues by turning on the console logging. Here's an example logger implementation. First, add a custom logger:

class ConsoleHttpPipelineLogger { constructor(minimumLogLevel) { this.minimumLogLevel = minimumLogLevel; } log(logLevel, message) { const logMessage = `${new Date().toISOString()} ${HttpPipelineLogLevel[logLevel]}: ${message}`; switch (logLevel) { case HttpPipelineLogLevel.ERROR: console.error(logMessage); break; case HttpPipelineLogLevel.WARNING: console.warn(logMessage); break; case HttpPipelineLogLevel.INFO: console.log(logMessage); break; } } }

Then when creating the QueueServiceClient instance, pass the logger in the options

const queueServiceClient = new QueueServiceClient( `https://${account}.queue.core.windows.net`, sharedKeyCredential, { logger: new ConsoleHttpPipelineLogger(HttpPipelineLogLevel.INFO) } );

If you have registered an application with an Azure Active Directory tenant, you can assign it to an RBAC role in your Azure Storage account. This enables you to use the Azure.Identity library to authenticate with Azure Storage as shown in the azureAdAuth.ts sample.

More code samples

This project welcomes contributions and suggestions. Most contributions require you to agree to aContributor License Agreement (CLA) declaring that you have the right to, and actually do, grant usthe rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to providea CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructionsprovided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct.For more information see the Code of Conduct FAQ orcontact opencode@microsoft.com with any additional questions or comments.

ncG1vNJzZmiZqqq%2Fpr%2FDpJuom6Njr627wWeaqKqVY8SqusOorqxmnprBcHDWnploopGrrrSv0aKnrWeRr8KzsYysq6iqkZyybr3UnqyeZ2Fne3F6j2anq52mnrK4epRooKecla17qcDMpQ%3D%3D