Global SDK Configuration Acceptance Criteria

As a software developer I need to provide a mechanism to set up the environment configuration so that values of the environment variables can be configured seamlessly for different environments like "Dev", "test", "production", etc.

There are different services provided by the node sdk such as:

service management storage blob table queue servicebus website management sql azure The user can use the global configuration and helper methods to configure settings for a particular environment say: "production"

azure.configure("production", function(c) { c.storage({ account: 'teststorage', key: '123456476546874687=='}); }); Now, the user needs to access the dev environment for which the storage account and the access key are different.

Note: The below is a much lower priority scenario

The values of configuration parameters can be changed without restarting the application

azure.configure("dev", function(c) { c.storage({account: 'teststorage1', key: 'AAAAA123456476546874687=='}); }); These changes will be observed when creating new objects that use that configuration parameter; existing objects will continue to use the ones they were created with.

Talk about: It also provides the concept of child configurations.

Talk about lookup.

Talk about acceptance criteria.