This release is a pre-release and may not be stable for production use.
Oracle Cloud (OCI) Resource Provider
The Oracle Cloud (OCI) Resource Provider lets you manage Oracle 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/oci
or yarn:
yarn add @pulumi/oci
Python
To use from Python, install using pip:
pip install pulumi_oci
Go
To use from Go, use go get to grab the latest version of the library:
go get github.com/pulumi/pulumi-oci/sdk/...
.NET
To use from .NET, install using dotnet add package:
dotnet add package Pulumi.Oci
Configuration
The following configuration points are available for the oci provider:
oci:tenancyOcid(environment:TF_VAR_tenancy_ocid) - OCID of your tenancy. To get the value, see [Where to Get the Tenancy's OCID and User's OCID](https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#five.oci:userOcid(environment:TF_VAR_user_ocid) - OCID of the user calling the API. To get the value, see Where to Get the Tenancy's OCID and User's OCID.oci:privateKey(environment:TF_VAR_private_key) - The contents of the private key file. Required ifprivateKeyPathis not defined, and takes precedence overprivateKeyPathif both are defined. For details on how to create and configure keys see How to Generate an API Signing Key) and How to Upload the Public Key.oci:privateKeyPath(environment:TF_VAR_private_key_path) - The path (including filename) of the private key stored on your computer. Required ifprivateKeyis not defined. For details on how to create and configure keys see How to Generate an API Signing Key) and How to Upload the Public Key.oci:privateKeyPassword(environment:TF_VAR_private_key_password) - Passphrase used for the key, if it is encrypted.oci:fingerprint(environment:TF_VAR_fingerprint) - Fingerprint for the key pair being used. To get the value, see How to Get the Key's Fingerprint.oci:region(environment:TF_VAR_region) - An OCI region. See Regions and Availability Domains.oci:configFileProfile(environment:TF_VAR_config_file_profile) - The profile name if you would like to use a custom profile in the OCI config file to provide the authentication credentials. See Using the SDK and CLI Configuration File for more information.
Reference
For detailed reference documentation, please visit the Pulumi registry.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-oci 0.0.1a1651101569
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.0.1a1651101569.tar.gz | 3.3 MB | Without provenance | Details for pulumi_oci-0.0.1a1651101569.tar.gz |
Release files / pulumi_oci-0.0.1a1651101569.tar.gz
| Download URL | pulumi_oci-0.0.1a1651101569.tar.gz |
|---|---|
| Size | 3.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62aa4134cf344617e83c09794bdce71054aa9fd007cdde209f150b0df9365121
|
|
BLAKE2b-256 checksum How to use checksums |
415b9dc2702217e9af1d309afacce9420f24ed0ca2a2304a1fec0b15f2eb57c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.7.12
|
Security for pulumi-oci 0.0.1a1651101569
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.
