Security News
New Python Packaging Proposal Aims to Solve Phantom Dependency Problem with SBOMs
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
@azure/arm-recoveryservices
Advanced tools
This package contains an isomorphic SDK (runs both in Node.js and in browsers) for Azure RecoveryServices client.
Recovery Services Client
Source code | Package (NPM) | API reference documentation | Samples
@azure/arm-recoveryservices
packageInstall the Azure RecoveryServices client library for JavaScript with npm
:
npm install @azure/arm-recoveryservices
RecoveryServicesClient
To create a client object to access the Azure RecoveryServices API, you will need the endpoint
of your Azure RecoveryServices resource and a credential
. The Azure RecoveryServices client can use Azure Active Directory credentials to authenticate.
You can find the endpoint for your Azure RecoveryServices resource in the Azure Portal.
You can authenticate with Azure Active Directory using a credential from the @azure/identity library or an existing AAD Token.
To use the DefaultAzureCredential provider shown below, or other credential providers provided with the Azure SDK, please install the @azure/identity
package:
npm install @azure/identity
You will also need to register a new AAD application and grant access to Azure RecoveryServices by assigning the suitable role to your service principal (note: roles such as "Owner"
will not grant the necessary permissions).
Set the values of the client ID, tenant ID, and client secret of the AAD application as environment variables: AZURE_CLIENT_ID
, AZURE_TENANT_ID
, AZURE_CLIENT_SECRET
.
For more information about how to create an Azure AD Application check out this guide.
const { RecoveryServicesClient } = require("@azure/arm-recoveryservices");
const { DefaultAzureCredential } = require("@azure/identity");
const subscriptionId = "00000000-0000-0000-0000-000000000000";
const client = new RecoveryServicesClient(new DefaultAzureCredential(), subscriptionId);
RecoveryServicesClient
is the primary interface for developers using the Azure RecoveryServices client library. Explore the methods on this client object to understand the different features of the Azure RecoveryServices service that you can access.
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.
Please take a look at the samples directory for detailed examples on how to use this library.
If you'd like to contribute to this library, please read the contributing guide to learn more about how to build and test the code.
FAQs
A generated SDK for RecoveryServicesClient.
The npm package @azure/arm-recoveryservices receives a total of 12,884 weekly downloads. As such, @azure/arm-recoveryservices popularity was classified as popular.
We found that @azure/arm-recoveryservices demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
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.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.