azure-sdk-for-js/sdk/devcenter/developer-devcenter-rest
Jeremy Meng a28e8f0795 [EngSys] move to vendored version of cross-env via dev-tool
***NO_CI***

- apply the transformation

- update samples' README
2024-11-02 00:48:06 +00:00
..
review [eslint-plugin] add rule "@typescript-eslint/consistent-type-imports": "warn" 2024-10-30 15:48:52 +00:00
samples [EngSys] move to vendored version of cross-env via dev-tool 2024-11-02 00:48:06 +00:00
samples-dev DevCenter Data Plane TypeSpec beta SDK v2023-04-01 (#27835) 2023-11-20 15:41:46 -08:00
src [eslint-plugin] add rule "@typescript-eslint/consistent-type-imports": "warn" 2024-10-30 15:48:52 +00:00
test/public [eslint-plugin] add rule "@typescript-eslint/consistent-type-imports": "warn" 2024-10-30 15:48:52 +00:00
CHANGELOG.md Post release automated changes for devcenter releases (#30335) 2024-07-08 15:33:01 -07:00
LICENSE Add Azure DevCenter Package (#23429) 2022-10-19 10:22:31 +08:00
README.md Dev Center Stable SDK (#29512) 2024-05-22 14:21:45 -07:00
api-extractor.json Dev Center Stable SDK (#29512) 2024-05-22 14:21:45 -07:00
assets.json [DevCenter] Update tsp latest commit (#30033) 2024-07-05 11:53:39 -07:00
eslint.config.mjs Apply automated migration to eslint flat config 2024-08-22 11:43:19 -07:00
karma.conf.js [EngSys] standardize OSS copyright header 2024-08-27 13:01:38 -07:00
package.json [EngSys] move `uglify-js` to dev-tool vendored 2024-10-30 18:01:20 +00:00
sample.env DevCenter Data Plane TypeSpec beta SDK v2023-04-01 (#27835) 2023-11-20 15:41:46 -08:00
tsconfig.browser.config.json Dev Center Stable SDK (#29512) 2024-05-22 14:21:45 -07:00
tsconfig.json [EngSys] remove tsconfig.package.json 2024-07-16 13:27:25 +00:00
tsp-location.yaml [DevCenter] Update tsp latest commit (#30033) 2024-07-05 11:53:39 -07:00
vitest.browser.config.ts [EngSys] standardize OSS copyright header 2024-08-27 13:01:38 -07:00
vitest.config.ts [EngSys] standardize OSS copyright header 2024-08-27 13:01:38 -07:00

README.md

Azure DevCenter REST client library for JavaScript

The Azure DevCenter library provides access to manage resources for Microsoft Dev Box and Azure Deployment Environments. This package enables managing developer machines and environments in Azure.

Use the package for Azure DevCenter to:

Create, access, manage, and delete Dev Box resources Create, deploy, manage, and delete Environment resources

DevCenter service

Please rely heavily on our REST client docs to use this library

Key links:

Getting started

Currently supported environments

  • LTS versions of Node.js

Prerequisites

  • You must have an Azure subscription to use this package.
  • You must have configured a DevCenter, Project, Network Connection, Dev Box Definition, and Pool before you can create Dev Boxes
  • You must have configured a DevCenter, Project, Catalog, and Environment Type before you can create Environments

Install the @azure-rest/developer-devcenter package

Install the Azure DevCenter REST client REST client library for JavaScript with npm:

npm install @azure-rest/developer-devcenter

Create and authenticate a AzureDeveloperDevCenterClient

To use an Azure Active Directory (AAD) token credential, provide an instance of the desired credential type obtained from the @azure/identity library.

To authenticate with AAD, you must first npm install @azure/identity

After setup, you can choose which type of credential from @azure/identity to use. As an example, DefaultAzureCredential can be used to authenticate the client.

Set the value of dev center endpoint as environment variable: DEVCENTER_ENDPOINT

Key Concepts

REST Client

This client is one of our REST clients. We highly recommend you read how to use a REST client here.

DevCenter Concepts

Dev Boxes refer to managed developer machines running in Azure. Dev Boxes are provisioned in Pools, which define the network and image used for a Dev Box.

Environments refer to templated developer environments, which combine a template (Catalog Item) and parameters, as well as an Environment Type which defines permissions and where the resources are deployed.

Troubleshooting

Logging

Enabling logging may help uncover useful information about failures. In order to see a log of HTTP requests and responses, set the AZURE_LOG_LEVEL environment variable to info. Alternatively, logging can be enabled at runtime by calling setLogLevel in the @azure/logger:

const { setLogLevel } = require("@azure/logger");

setLogLevel("info");

For more detailed instructions on how to enable logs, you can look at the @azure/logger package docs.