cjs-forms
v0.0.1
Published
Azure Template client library samples for JavaScript
Downloads
3
Readme
Azure Template client library samples for JavaScript
This is an example header text. It will appear at the top of the README file.
These sample programs show how to use the JavaScript client libraries for Azure Template in some common scenarios.
| File Name | Description | | ----------------------------------------------------- | ------------------------------------ | | getConfigurationSetting.js | a succinct and simple sample example |
Prerequisites
The sample programs are compatible with LTS versions of Node.js.
You need an Azure subscription and the following Azure resources to run these sample programs:
This text will appear as part of the prerequisites.
Samples retrieve credentials to access the service endpoint from environment variables. Alternatively, edit the source code to include the appropriate credentials. See each individual sample for details on which environment variables/credentials it requires to function.
Adapting the samples to run in the browser may require some additional consideration. For details, please see the package README.
Setup
To run the samples using the published version of the package:
- Install the dependencies using
npm
:
npm install
Edit the file
sample.env
, adding the correct credentials to access the Azure service and run the samples. Then rename the file fromsample.env
to just.env
. The sample programs will read this file automatically.Run whichever samples you like (note that some samples may require additional setup, see the table above):
node getConfigurationSetting.js
Alternatively, run a single sample with the correct environment variables set (setting up the .env
file is not required if you do this), for example (cross-platform):
npx cross-env MY_VARIABLE="<my variable>" node getConfigurationSetting.js
Next Steps
Take a look at our API Documentation for more information about the APIs that are available in the clients.
This is an example footer text. It will appear at the bottom of the README file.