
Security News
Crates.io Implements Trusted Publishing Support
Crates.io adds Trusted Publishing support, enabling secure GitHub Actions-based crate releases without long-lived API tokens.
@azure/arm-billingbenefits
Advanced tools
This package contains an isomorphic SDK (runs both in Node.js and in browsers) for Azure BillingBenefitsRp client.
Azure Benefits RP let users create and manage benefits like savings plan.
Source code | Package (NPM) | API reference documentation | Samples
See our support policy for more details.
@azure/arm-billingbenefits
packageInstall the Azure BillingBenefitsRp client library for JavaScript with npm
:
npm install @azure/arm-billingbenefits
BillingBenefitsRP
To create a client object to access the Azure BillingBenefitsRp API, you will need the endpoint
of your Azure BillingBenefitsRp resource and a credential
. The Azure BillingBenefitsRp client can use Azure Active Directory credentials to authenticate.
You can find the endpoint for your Azure BillingBenefitsRp 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 BillingBenefitsRp 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 { BillingBenefitsRP } = require("@azure/arm-billingbenefits");
const { DefaultAzureCredential } = require("@azure/identity");
// For client-side applications running in the browser, use InteractiveBrowserCredential instead of DefaultAzureCredential. See https://aka.ms/azsdk/js/identity/examples for more details.
const subscriptionId = "00000000-0000-0000-0000-000000000000";
const client = new BillingBenefitsRP(new DefaultAzureCredential(), subscriptionId);
// For client-side applications running in the browser, use this code instead:
// const credential = new InteractiveBrowserCredential({
// tenantId: "<YOUR_TENANT_ID>",
// clientId: "<YOUR_CLIENT_ID>"
// });
// const client = new BillingBenefitsRP(credential, subscriptionId);
To use this client library in the browser, first you need to use a bundler. For details on how to do this, please refer to our bundling documentation.
BillingBenefitsRP
is the primary interface for developers using the Azure BillingBenefitsRp client library. Explore the methods on this client object to understand the different features of the Azure BillingBenefitsRp 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 BillingBenefitsRP.
The npm package @azure/arm-billingbenefits receives a total of 545 weekly downloads. As such, @azure/arm-billingbenefits popularity was classified as not popular.
We found that @azure/arm-billingbenefits demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Crates.io adds Trusted Publishing support, enabling secure GitHub Actions-based crate releases without long-lived API tokens.
Research
/Security News
Undocumented protestware found in 28 npm packages disrupts UI for Russian-language users visiting Russian and Belarusian domains.
Research
/Security News
North Korean threat actors deploy 67 malicious npm packages using the newly discovered XORIndex malware loader.