This release is a pre-release and may not be stable for production use.
New Relic Provider
The New Relic resource provider for Pulumi lets you use New Relic resources in your cloud programs. To use this package, please install the Pulumi CLI first.
Installing
This package is available in many languages in the standard packaging formats.
Node.js (Java/TypeScript)
To use from JavaScript or TypeScript in Node.js, install using either npm:
$ npm install @pulumi/newrelic
or yarn:
$ yarn add @pulumi/newrelic
Python
To use from Python, install using pip:
$ pip install pulumi_newrelic
Go
To use from Go, use go get to grab the latest version of the library
$ go get github.com/pulumi/pulumi-newrelic/sdk/v4
.NET
To use from .NET, install using dotnet add package:
$ dotnet add package Pulumi.Newrelic
Configuration
The following configuration points are available:
newrelic:apiKey- Your New Relic API key. TheNEW_RELIC__API_KEYenvironment variable can also be used.newrelic:adminApiKey- Your New Relic Admin API key. TheNEW_RELIC_ADMIN_API_KEYenvironment variable can also be used.newrelic:region- The region for the data center for which your New Relic account is configured. The New Relic region can also be set via the environment variableNEW_RELIC_REGION. Valid values areUSorEU. Only one region per provider block can be configured. If you have accounts in both regions, you must instantiate two providers - one for US and one for EUnewrelic:insecureSkipVerify- Trust self-signed SSL certificates. If omitted, theNEW_RELIC__API_SKIP_VERIFYenvironment variable is used.newrelic:insightsInsertKey- Your Insights insert key used when inserting Insights events via theinsights.Eventresource. Can also useNEW_RELIC__INSIGHTS_INSERT_KEYenvironment variable.newrelic:insightsInsertUrl- This argument changes the Insights insert URL (default ishttps://insights-collector.newrelic.com/v1/accounts). If the New Relic account is in the EU, the Insights API URL must be set tohttps://insights-collector.eu.newrelic.com/v1.newrelic:caCerts- A path to a PEM-encoded certificate authority used to verify the remote agent's certificate. TheNEW_RELIC__API_CACERTenvironment variable can also be used.
Reference
For further information, please visit the NewRelic provider docs or for detailed reference documentation, please visit the API docs.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-newrelic 4.16.0a1653606118
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pulumi_newrelic-4.16.0a1653606118.tar.gz | 125.3 kB | Without provenance | Details for pulumi_newrelic-4.16.0a1653606118.tar.gz |
Release files / pulumi_newrelic-4.16.0a1653606118.tar.gz
| Download URL | pulumi_newrelic-4.16.0a1653606118.tar.gz |
|---|---|
| Size | 125.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0011358638db55a2849087d12bbf4c0c69076abcdd18d833096b7a2dba91d888
|
|
BLAKE2b-256 checksum How to use checksums |
6796e63f2e8620e73ed18449d0a6e2b9d96b2a7db5b57da6248f1447623297c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.7.13
|
Security for pulumi-newrelic 4.16.0a1653606118
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
