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/go/...
Configuration
The following configuration points are available:
newrelic:apiKey- Your New Relic API key. TheNEWRELIC_API_KEYenvironment variable can also be used.newrelic:apiUrl- This argument changes the main REST API URL (default ishttps://api.newrelic.com/v2). If the New Relic account is in the EU, the API URL must be set tohttps://api.eu.newrelic.com/v2. TheNEWRELIC_API_URLenvironment variable can also be used.newrelic:syntheticsApiUrl- This argument changes the Synthetics API URL (default ishttps://synthetics.newrelic.com/synthetics/api/v3). If the New Relic account is in the EU. the API URL must be set tohttps://synthetics.eu.newrelic.com/synthetics/api/v3. TheNEWRELIC_SYNTHETICS_API_URLenvironment variable can also be used. This URL is used to provision Synthetics monitors and monitor scripts only.newrelic:infraApiUrl- This argument changes the Infrastructure API URL (default ishttps://infra-api.newrelic.com/v2). If the New Relic account is in the EU, the Infra API URL must be set tohttps://infra-api.eu.newrelic.com/v2. TheNEWRELIC_INFRA_API_URLenvironment variable can also be used. This URL is used to provision Infrastructure alert conditions only.newrelic:insecureSkipVerify- Trust self-signed SSL certificates. If omitted, theNEWRELIC_API_SKIP_VERIFYenvironment variable is used.newrelic:insightsAccountId- Your New Relic Account ID used when inserting Insights events via theinsights.Eventresource. Can also useNEWRELIC_INSIGHTS_ACCOUNT_IDenvironment variable.newrelic:insightsInsertKey- Your Insights insert key used when inserting Insights events via theinsights.Eventresource. Can also useNEWRELIC_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. TheNEWRELIC_INSIGHTS_INSERT_URLenvironment variable can also be used.newrelic:caCerts- A path to a PEM-encoded certificate authority used to verify the remote agent's certificate. TheNEWRELIC_API_CACERTenvironment variable can also be used.
Reference
For detailed reference documentation, please visit the API docs.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-newrelic 2.1.0a1588029277
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-2.1.0a1588029277.tar.gz | 23.4 kB | Without provenance | Details for pulumi_newrelic-2.1.0a1588029277.tar.gz |
Release files / pulumi_newrelic-2.1.0a1588029277.tar.gz
| Download URL | pulumi_newrelic-2.1.0a1588029277.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1c5de7bc0adbdb85c212a32bdf654eab771120f486f8756cf242e1a53fe3f5c
|
|
BLAKE2b-256 checksum How to use checksums |
275ee2a7f6605799d4b4d3a0ac82ce9e88fe060096636fc7658f02ab2823383a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.6.7
|
Security for pulumi-newrelic 2.1.0a1588029277
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.
