This release is a pre-release and may not be stable for production use.
Splunk Resource Provider
The Splunk Resource Provider lets you manage Splunk resources.
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/splunk
or yarn:
$ yarn add @pulumi/splunk
Python
To use from Python, install using pip:
$ pip install pulumi_splunk
Go
To use from Go, use go get to grab the latest version of the library
$ go get github.com/pulumi/pulumi-splunk/sdk
.NET
To use from .NET, install using dotnet add package:
$ dotnet add package Pulumi.Splunk
Configuration
The following configuration points are available:
splunk:url- (Required) The URL for the Splunk instance to be configured. (The provider useshttpsas the default schema as prefix to the URL) It can also be sourced from theSPLUNK_URLenvironment variable.splunk:username- (Optional) The username to access the Splunk instance to be configured. It can also be sourced from theSPLUNK_USERNAMEenvironment variable.splunk:password- (Optional) The password to access the Splunk instance to be configured. It can also be sourced from theSPLUNK_PASSWORDenvironment variable.splunk:authToken- (Optional) Use auth token instead of username and password to configure Splunk instance. If specified, auth token takes priority over username/password. It can also be sourced from theSPLUNK_AUTH_TOKENenvironment variable.splunk:insecureSkipVerify-(Optional) Insecure skip verification flag (Defaults totrue) It can also be sourced from theSPLUNK_INSECURE_SKIP_VERIFYenvironment variable.splunk:timeout- (Optional) Timeout when making calls to Splunk server. (Defaults to60 seconds) It can also be sourced from theSPLUNK_TIMEOUTenvironment variable.
Reference
For further information, please visit the Splunk provider docs or for detailed reference documentation, please visit the API docs.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-splunk 1.6.0a1792478501
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 | |
|---|---|---|---|---|
| pulumi_splunk-1.6.0a1792478501.tar.gz | 172.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulumi_splunk-1.6.0a1792478501-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 377.1 kB
Release files / pulumi_splunk-1.6.0a1792478501.tar.gz
| Download URL | pulumi_splunk-1.6.0a1792478501.tar.gz |
|---|---|
| Size | 172.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5fb540e5f8c96cef9fbfd4f262711c17604b717da5fdf5ab0f0fceaa702f22ef
|
|
BLAKE2b-256 checksum How to use checksums |
0207bd3d68c761f17a14f4596e330e236625d6a4aa2d1dee26a79b53f5a2c3d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / pulumi_splunk-1.6.0a1792478501-py3-none-any.whl
| Download URL | pulumi_splunk-1.6.0a1792478501-py3-none-any.whl |
|---|---|
| Size | 204.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f833aaa759c951b8c3183fd212e27121f847c97bd22ebe3ab5d0301e6f0b3f64
|
|
BLAKE2b-256 checksum How to use checksums |
39a9ccca5706d627c29a29c4a5421edaea37015f68fa9bf6b1df19af78cdcaf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for pulumi-splunk 1.6.0a1792478501
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.
