
Research
Security News
Malicious PyPI Package Exploits Deezer API for Coordinated Music Piracy
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
@azure/arm-containerservice
Advanced tools
A generated SDK for ContainerServiceClient.
This package contains an isomorphic SDK (runs both in Node.js and in browsers) for Azure ContainerService client.
The Container Service Client.
Source code | Package (NPM) | API reference documentation | Samples
See our support policy for more details.
@azure/arm-containerservice
packageInstall the Azure ContainerService client library for JavaScript with npm
:
npm install @azure/arm-containerservice
ContainerServiceClient
To create a client object to access the Azure ContainerService API, you will need the endpoint
of your Azure ContainerService resource and a credential
. The Azure ContainerService client can use Azure Active Directory credentials to authenticate.
You can find the endpoint for your Azure ContainerService 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 ContainerService by assigning the suitable role to your service principal (note: roles such as "Owner"
will not grant the necessary permissions).
For more information about how to create an Azure AD Application check out this guide.
const { ContainerServiceClient } = require("@azure/arm-containerservice");
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 ContainerServiceClient(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 ContainerServiceClient(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.
ContainerServiceClient
is the primary interface for developers using the Azure ContainerService client library. Explore the methods on this client object to understand the different features of the Azure ContainerService 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 ContainerServiceClient.
The npm package @azure/arm-containerservice receives a total of 25,930 weekly downloads. As such, @azure/arm-containerservice popularity was classified as popular.
We found that @azure/arm-containerservice 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.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.
Security News
Newly introduced telemetry in devenv 1.4 sparked a backlash over privacy concerns, leading to the removal of its AI-powered feature after strong community pushback.