Files
Jeremy MengandGitHub 696aa6ae52 [EngSys] remove dev-tool run vendored from individual packages (#36198)
The primary reason that we added `dev-tool run vendored` command is to manage
dependencies centrally. Now we can achieve that with pnpm workspace/catalog
feature. This PR removes most of the `dev-tool run vendored` usages from
individual packages and replace them with direct tool calls. Those tools are
also added to individual package's dev dependencies per Pnpm recommendation.
2025-10-13 16:52:42 -07:00

6.3 KiB

@azure/arm-devopsinfrastructure client library samples for JavaScript

These sample programs show how to use the JavaScript client libraries for @azure/arm-devopsinfrastructure in some common scenarios.

File Name Description
imageVersionsListByImageSample.js list ImageVersion resources by Image x-ms-original-file: 2024-10-19/ImageVersions_ListByImage.json
operationsListSample.js list the operations for the provider x-ms-original-file: 2024-10-19/ListOperations.json
poolsCreateOrUpdateSample.js create a Pool x-ms-original-file: 2024-10-19/CreateOrUpdatePool.json
poolsDeleteSample.js delete a Pool x-ms-original-file: 2024-10-19/DeletePool.json
poolsGetSample.js get a Pool x-ms-original-file: 2024-10-19/GetPool.json
poolsListByResourceGroupSample.js list Pool resources by resource group x-ms-original-file: 2024-10-19/ListPoolsBySubscriptionAndResourceGroup.json
poolsListBySubscriptionSample.js list Pool resources by subscription ID x-ms-original-file: 2024-10-19/ListPoolsBySubscription.json
poolsUpdateSample.js update a Pool x-ms-original-file: 2024-10-19/UpdatePool.json
resourceDetailsListByPoolSample.js list ResourceDetailsObject resources by Pool x-ms-original-file: 2024-10-19/ResourceDetails_ListByPool.json
skuListByLocationSample.js list ResourceSku resources by subscription ID x-ms-original-file: 2024-10-19/Sku_ListByLocation.json
subscriptionUsagesUsagesSample.js list Quota resources by subscription ID x-ms-original-file: 2024-10-19/SubscriptionUsages_Usages.json

Prerequisites

The sample programs are compatible with LTS versions of Node.js.

You need an Azure subscription to run these sample programs.

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:

  1. Install the dependencies using npm:
npm install
  1. Edit the file sample.env, adding the correct credentials to access the Azure service and run the samples. Then rename the file from sample.env to just .env. The sample programs will read this file automatically.

  2. Run whichever samples you like (note that some samples may require additional setup, see the table above):

node imageVersionsListByImageSample.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):

cross-env node imageVersionsListByImageSample.js

Next Steps

Take a look at our API Documentation for more information about the APIs that are available in the clients.