[Storage] Support SAS Connection String - storage-queue

[HarshaNalluru]

Adds a new environment variable - "STORAGE_SAS_CONNECTION_STRING"

Storage service provides two types of connection strings, one with the accountname and key and the other one SAS conn. string with SAS string and endpoints.

This PR adds the SAS connection string support to the existing connection string static methods and constructors.

Handled SAS connection string in the recorder and added tests and recordings accordingly.

Changes in this PR

• Everything except the recordings -
  https://github.com/Azure/azure-sdk-for-js/pull/4372/files?file-filters%5B%5D=.env&file-filters%5B%5D=.ts
• Only the recordings -
  https://github.com/Azure/azure-sdk-for-js/pull/4372/files?file-filters%5B%5D=.js&file-filters%5B%5D=.json

[XiaoningLiu]

const matchCredentials = connectionString.match [](start = 4, length = 47)

May not related to this CR about SAS connection string. But seems this kind of connection string cannot be successfully parsed:

DefaultEndpointsProtocol=https;
BlobEndpoint=[http://www.mydomain.com](http://www.mydomain.com);
AccountName=storagesample;
AccountKey=<account-key>

https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#create-a-connection-string-for-an-explicit-storage-endpoint

[HarshaNalluru]

I'm under the impression that connection string can only be of the following type.

DefaultEndpointsProtocol=[http|https];
AccountName=myAccountName;
AccountKey=myAccountKey;
EndpointSuffix=mySuffix;

And this is what the portal provides from what I know.
Keeping this in mind, we had the logic of parsing the connection strings.

[HarshaNalluru]

We can definitely add support to cover a wider range of connection strings.
You want me to do it in the same PR or create a new issue for it?

[XiaoningLiu]

Both fine to me. Just what you prefer : )

[HarshaNalluru]

Created a new issue - #4578

[XiaoningLiu]

getSASConnectionStringFromEnvironment [](start = 6, length = 37)

Can we generate a SAS connection string dynamically using storage account & key in Node.js runtime?

Account Name + Account Key => SAS

So we can reuse current account_name and account_key environment variable, instead of importing a new environment variable.

SAS aims for a short term period access, and can be oudated when storage key is rotated. Also a SAS has a valid period, after that, SAS will be outdated.

In browser runtime, we can use the environment variable account_name with account_sas to generate the SAS connection string too.

[HarshaNalluru]

Sure, we can do that. I'll update.

[XiaoningLiu]

Can we generate a SAS connection string dynamically using storage account & key in Node.js runtime?

Account Name + Account Key => SAS

So we can reuse current account_name and account_key environment variable, instead of importing a new REQUIRED environment variable.

SAS aims for a short term period access, and can be oudated when storage key is rotated. Also a SAS has a valid period, after that, SAS will be outdated.

In browser runtime, we can reuse existing environment variables account_name with account_sas to generate the SAS connection string too.

[XiaoningLiu]

Looks good. My major concern is about the new introduced REQUIRED environment variable for SAS connection string. Basically we can generate a SAS connection string based on existing environment variabless like account name and account key in node.js runtime, or account_name and account_sas in browsers.

[bterlson]

Looks good though I agree with removing the new environment variable if possible (if it isn't, let me know).

[XiaoningLiu]

Where does this get referred?

[HarshaNalluru]

sample.env is just a file to show how the environment(or .env file) should look like.

STORAGE_CONNECTION_STRING environment variable is being used in some of the tests where we test the connection string static methods and constructors. [Unrelated to this PR]