From 1a4cfbc7819b54c73bd7d40eed01f3c60579e203 Mon Sep 17 00:00:00 2001 From: Ramon Quitales Date: Mon, 2 Dec 2024 14:07:55 -0800 Subject: [PATCH] Fix wrong env var for OCI insights esc setup (#13481) --- content/docs/pulumi-cloud/insights/accounts.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/docs/pulumi-cloud/insights/accounts.md b/content/docs/pulumi-cloud/insights/accounts.md index ab48dcbb1a1b..25c409ef76c6 100644 --- a/content/docs/pulumi-cloud/insights/accounts.md +++ b/content/docs/pulumi-cloud/insights/accounts.md @@ -191,6 +191,7 @@ The OCI scanner for Pulumi Cloud requires access to your Oracle Cloud account. T * **OCI_FINGERPRINT**: Fingerprint for the key pair being used. See [How to Get the Key's Fingerprint](https://docs.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm#four). * **OCI_REGION**: The OCI region where your resources are located. See [Regions and Availability Domains](https://docs.oracle.com/iaas/Content/General/Concepts/regions.htm). * **OCI_PRIVATE_KEY_PATH**: The private key is required to be listed as an ESC file. To create a private key and integrate it with ESC, see [How to Generate an API Signing Key](https://docs.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm#two) and [how to upload the public key](https://docs.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm#three) + Use the following ESC configuration to provide the required credentials: ```yaml @@ -201,7 +202,7 @@ values: OCI_TENANCY_OCID: "ocid1.tenancy.oc1..tenancyidnumbers" OCI_USER_OCID: "user_ocid" files: - OCI_PRIVATE_KEY: "PRIVATE_KEY_CONTENT" + OCI_PRIVATE_KEY_PATH: "" ``` Once the ESC environment is set up with the proper credentials, assign it to your insights account during the account creation phase.