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
To use uv instead:
uv 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/v5/...
.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:auth |
The type of auth to use. Options are 'ApiKey', 'SecurityToken', 'InstancePrincipal', 'ResourcePrincipal' and 'OKEWorkloadIdentity'. By default, 'ApiKey' will be used. | |
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 5.4.0
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_oci-5.4.0.tar.gz | 12.1 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulumi_oci-5.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.2 MB
Release files / pulumi_oci-5.4.0.tar.gz
| Download URL | pulumi_oci-5.4.0.tar.gz |
|---|---|
| Size | 12.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97bae26e98107bdff7c28ddeadf92676fc4eb1eb513dcd7db86de41d868e14a4
|
|
BLAKE2b-256 checksum How to use checksums |
279dd7eafbc262d575fb67f0d80869c9428fda012b2691e2131a110131963e4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / pulumi_oci-5.4.0-py3-none-any.whl
| Download URL | pulumi_oci-5.4.0-py3-none-any.whl |
|---|---|
| Size | 17.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f05740f030c7f8c0f2f823c7059b761c7775a18c9dc217a32183336335a3075
|
|
BLAKE2b-256 checksum How to use checksums |
bae64d6bab0c3e7e266d46f7e72193a8becbfe9663524758e5c9d783e0913203
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for pulumi-oci 5.4.0
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.
