oraclecloud-ci-integration

# Oracle Cloud CI Integration ## Overview Set up GitHub Actions workflows that authenticate to OCI, run Terraform plans, and execute tests against OCI services. The OCI Terraform provider has known bugs — notably ResourcePrincipal forcing the wrong region (#1761) — that require specific workarounds. This skill provides battle-tested CI patterns that avoid those pitfalls. **Purpose:** Get a working CI pipeline that authenticates to OCI, runs Terraform safely, and tests OCI-dependent code without flaky failures. ## Prerequisites - **OCI tenancy** with an API signing key configured in `~/.oci/config` - **Terraform >= 1.5** and the OCI provider (`oracle/oci`) - **GitHub repository** with Actions enabled - **GitHub Secrets** configured: `OCI_USER_OCID`, `OCI_FINGERPRINT`, `OCI_TENANCY_OCID`, `OCI_REGION`, `OCI_PRIVATE_KEY` (PEM contents, base64-encoded) - **Python 3.8+** with `pip install oci` for SDK-based tests ## Instructions ### Step 1: Configure GitHub Secrets for OCI Auth OCI API key authentication requires five values. Store them as GitHub repository secrets: ```bash # Encode your private key for safe storage in GitHub Secrets base64 -w 0 ~/.oci/oci_api_key.pem # Copy output → GitHub Settings > Secrets > OCI_PRIVATE_KEY ``` The remaining secrets come from your `~/.oci/config` file: `user`, `fingerprint`, `tenancy`, and `region`. ### Step 2: GitHub Actions Workflow with Terraform Create `.github/workflows/oci-terraform.yml`: ```yaml name: OCI Terraform on: pus...