Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →

@azure/arm-appservice-profile-2019-03-01-hybrid

Package Overview

Dependencies

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

@azure/arm-appservice-profile-2019-03-01-hybrid

WebSiteManagementClient Library with typescript type definitions for node.js and browser.

1.2.0
latest
Source
npm

Version published: 3 years ago

Weekly downloads: 20; increased by5.26%

Maintainers: 1

Weekly downloads

Created: 6 years ago

Source

Azure WebSiteManagementClient SDK for JavaScript

This package contains an isomorphic SDK (runs both in Node.js and in browsers) for WebSiteManagementClient.

Please note, this package is deprecated and not functional as it uses an older version of the Javascript SDK generator. As of April 2022, you can instead use @azure/arm-appservice-profile-2020-09-01-hybrid.

Currently supported environments

LTS versions of Node.js
Latest versions of Safari, Chrome, Edge, and Firefox.

Prerequisites

You must have an Azure subscription.

How to install

To use this SDK in your project, you will need to install two packages.

@azure/arm-appservice-profile-2019-03-01-hybrid that contains the client.
@azure/identity that provides different mechanisms for the client to authenticate your requests using Azure Active Directory.

Install both packages using the below command:

npm install --save @azure/arm-appservice-profile-2019-03-01-hybrid @azure/identity

Note: You may have used either @azure/ms-rest-nodeauth or @azure/ms-rest-browserauth in the past. These packages are in maintenance mode receiving critical bug fixes, but no new features. If you are on a Node.js that has LTS status, or are writing a client side browser application, we strongly encourage you to upgrade to @azure/identity which uses the latest versions of Azure Active Directory and MSAL APIs and provides more authentication options.

How to use

If you are writing a client side browser application,
- Follow the instructions in the section on Authenticating client side browser applications in Azure Identity examples to register your application in the Microsoft identity platform and set the right permissions.
- Copy the client ID and tenant ID from the Overview section of your app registration in Azure portal and use it in the browser sample below.
If you are writing a server side application,
- Select a credential from @azure/identity based on the authentication method of your choice
- Complete the set up steps required by the credential if any.
- Use the credential you picked in the place of DefaultAzureCredential in the Node.js sample below.

In the below samples, we pass the credential and the Azure subscription id to instantiate the client. Once the client is created, explore the operations on it either in your favorite editor or in our API reference documentation to get started.

nodejs - Authentication, client creation, and list certificates as an example written in JavaScript.

Sample code

const { DefaultAzureCredential } = require("@azure/identity");
const { WebSiteManagementClient } = require("@azure/arm-appservice-profile-2019-03-01-hybrid");
const subscriptionId = process.env["AZURE_SUBSCRIPTION_ID"];

// Use `DefaultAzureCredential` or any other credential of your choice based on https://aka.ms/azsdk/js/identity/examples
// Please note that you can also use credentials from the `@azure/ms-rest-nodeauth` package instead.
const creds = new DefaultAzureCredential();
const client = new WebSiteManagementClient(creds, subscriptionId);

client.certificates.list().then((result) => {
  console.log("The result is:");
  console.log(result);
}).catch((err) => {
  console.log("An error occurred:");
  console.error(err);
});

browser - Authentication, client creation, and list certificates as an example written in JavaScript.

In browser applications, we recommend using the InteractiveBrowserCredential that interactively authenticates using the default system browser.

See Single-page application: App registration guide to configure your app registration for the browser.
Note down the client Id from the previous step and use it in the browser sample below.

Sample code

index.html

<!DOCTYPE html>
<html lang="en">
  <head>
    <title>@azure/arm-appservice-profile-2019-03-01-hybrid sample</title>
    <script src="node_modules/@azure/ms-rest-azure-js/dist/msRestAzure.js"></script>
    <script src="node_modules/@azure/identity/dist/index.js"></script>
    <script src="node_modules/@azure/arm-appservice-profile-2019-03-01-hybrid/dist/arm-appservice-profile-2019-03-01-hybrid.js"></script>
    <script type="text/javascript">
      const subscriptionId = "<Subscription_Id>";
      // Create credentials using the `@azure/identity` package.
      // Please note that you can also use credentials from the `@azure/ms-rest-browserauth` package instead.
      const credential = new InteractiveBrowserCredential(
      {
        clientId: "<client id for your Azure AD app>",
        tenantId: "<optional tenant for your organization>"
      });
      const client = new Azure.ArmAppserviceProfile20190301Hybrid.WebSiteManagementClient(creds, subscriptionId);
      client.certificates.list().then((result) => {
        console.log("The result is:");
        console.log(result);
      }).catch((err) => {
        console.log("An error occurred:");
        console.error(err);
      });
    </script>
  </head>
  <body></body>
</html>

Microsoft Azure SDK for Javascript

Keywords

FAQs

What is @azure/arm-appservice-profile-2019-03-01-hybrid?

Is @azure/arm-appservice-profile-2019-03-01-hybrid popular?

Is @azure/arm-appservice-profile-2019-03-01-hybrid well maintained?

Package last updated on 27 Apr 2022

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install