This release is a pre-release and may not be stable for production use.
Elastic Cloud Resource Provider
The Elastic Cloud Resource Provider lets you manage Elastic Cloud resources.
Installing
This package is available for several languages/platforms:
Node.js (JavaScript/TypeScript)
To use from JavaScript or TypeScript in Node.js, install using either npm:
npm install @pulumi/ec
or yarn:
yarn add @pulumi/ec
Python
To use from Python, install using pip:
pip install pulumi_ec
Go
To use from Go, use go get to grab the latest version of the library:
go get github.com/pulumi/pulumi-ec/sdk
.NET
To use from .NET, install using dotnet add package:
dotnet add package Pulumi.ElasticCloud
Configuration
The following configuration points are available for the ec provider:
ec:endpoint: The Elastic Cloud endpoint to which requests should be sent. This value should be specified only when using the Elastic Cloud provider with an ECE installation or ESS Private.ec:apikey: The Elastic Cloud API key, recommended overusernameandpasswordto authenticate against the Elastic Cloud API. May also be sourced from environment variableEC_API_KEY.ec:username: The Elastic Cloud username. May also be sourced from environment variableEC_USERorEC_USERNAME. Conflicts withec:apiKey. Not recommened - prefer usingec:apikeyoverec:usernameandec:password.ec:password: The Elastic Cloud user's password. May also be sourced from environment variableEC_PASSorEC_PASSWORD. Conflicts withec:apiKey. Not recommened - prefer usingec:apikeyoverec:usernameandec:password.ec:insecure: Iftrue, allows the provider to skip TLS verification (not recommended). Defaults tofalse.ec:timeout: Allows the user to set a custom timeout in the individual HTTP request level. Defaults to 1 minute ("1m"), but can be extended if timeouts are experienced.ec:verbose: When set to true, it writes a requests.json file in the folder where Terraform runs with all the outgoing HTTP requests and responses. Defaults to false.ec:verboseCredentials: If set totrueandec:verboseis set totrue, the contents of the Authorization header will not be redacted. Defaults tofalse.ec:verboseFile: Sets the name of the file to which verbose request and response HTTP flow will be written. Defaults torequest.log.
Either ec:endpoint or (ec:username and ec:password) must be specified. All other parameters are optional:
Reference
For detailed reference documentation, please visit the Pulumi registry.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-ec 1.0.0a1768432976
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_ec-1.0.0a1768432976.tar.gz | 80.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulumi_ec-1.0.0a1768432976-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 183.3 kB
Release files / pulumi_ec-1.0.0a1768432976.tar.gz
| Download URL | pulumi_ec-1.0.0a1768432976.tar.gz |
|---|---|
| Size | 80.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b89970986047836847693cecc0e767550822c22c38164edd6de05a4ef1e7a4fb
|
|
BLAKE2b-256 checksum How to use checksums |
b0d140f28fb6be61db9f3c2969256c963c9d942fdac27a21ff379ce41381b01c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.8
|
Release files / pulumi_ec-1.0.0a1768432976-py3-none-any.whl
| Download URL | pulumi_ec-1.0.0a1768432976-py3-none-any.whl |
|---|---|
| Size | 103.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db55f396477b50778b1fc4af2c3190fe8bc73ba0eb85b0bb9c2f9a807452c945
|
|
BLAKE2b-256 checksum How to use checksums |
e8b52406a281966c29e140a328b59d016f4ebb6cc8aeaf0c66d43c4ad7545206
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.8
|
Security for pulumi-ec 1.0.0a1768432976
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.
