This release is a pre-release and may not be stable for production use.
Oracle Cloud Infrastructure Resource Provider
The Oracle Cloud Infrastructure (OCI) Resource Provider lets you manage OCI resources.
Installing
This package is available for several languages/platforms:
Node.js (JavaScript/TypeScript)
To use with JavaScript or TypeScript in Node.js, install using either npm:
npm install @pulumi/oci
or yarn:
yarn add @pulumi/oci
Python
To use with Python, install using pip:
python3 -m pip install pulumi_oci
Go
To use with Go, use go get to grab the latest version of the library:
go get github.com/pulumi/pulumi-oci/sdk/...
.NET
To use with .NET, install using dotnet add package:
dotnet add package Pulumi.Oci
Configuration
The following configuration options are available for the oci provider:
| Option | Environment variable | Description |
|---|---|---|
oci:tenancyOcid |
TF_VAR_tenancy_ocid |
OCID of your tenancy. |
oci:userOcid |
TF_VAR_user_ocid |
OCID of the user calling the API. |
oci:privateKey |
TF_VAR_private_key |
The contents of the private key file. Required if privateKeyPath is not defined and takes precedence if both are defined. |
oci:privateKeyPath |
TF_VAR_private_key_path |
The path (including filename) of the private key stored on your computer. Required if privateKey is not defined. |
oci:privateKeyPassword |
TF_VAR_private_key_password |
Passphrase used for the key, if it is encrypted. |
oci:fingerprint |
TF_VAR_fingerprint |
Fingerprint for the key pair being used. |
oci:region |
TF_VAR_region |
An OCI region. |
oci:configFileProfile |
TF_VAR_config_file_profile |
The custom profile to use instead of the DEFAULT profile in .oci/config. |
Use the Required Keys and OCIDs chapter of the OCI Developer Guide to learn:
- How to Generate an API Signing Key
- How to Get the Key's Fingerprint
- Where to Get the Tenancy's OCID and User's OCID
Reference
For detailed reference documentation, please visit the Pulumi registry.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-oci 0.2.1a1660649476
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_oci-0.2.1a1660649476.tar.gz | 3.8 MB | Without provenance | Details for pulumi_oci-0.2.1a1660649476.tar.gz |
Release files / pulumi_oci-0.2.1a1660649476.tar.gz
| Download URL | pulumi_oci-0.2.1a1660649476.tar.gz |
|---|---|
| Size | 3.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29932a01e35293263620d3f4911cba4576f6ff5fc29c9119b150a54f06d763b6
|
|
BLAKE2b-256 checksum How to use checksums |
7d7194dccb48fa90d31d437948d3f5654944bc912eb1962f6b6fe95e3690981e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Security for pulumi-oci 0.2.1a1660649476
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.
