Terraform with Oracle Cloud Infrastructure and Jenkins — Lesson 1: OCI Provider, Compartments, Authentication, and Terraform Setup

Technical Scope

• OCI tenancy, compartments, regions, and availability domains
• API key, configuration, and workload identity concepts
• Terraform OCI provider and provider aliases
• Repository setup, inputs, tagging, and plan verification

Instructor Demonstration

Initialize Terraform against a controlled OCI compartment and verify tenancy context.

Applied Workshop

Create a provider configuration that supports separate test and production compartments.

1. Translate the scenario into configuration, access, state, pipeline, or module decisions.
2. Implement the change in a controlled workspace or repository.
3. Capture the plan, logs, outputs, policy results, and post-change checks.
4. Explain one safer or more maintainable alternative and its trade-off.

Validation Standard

The plan targets the correct tenancy, region, and compartment without embedded secrets.

• The intended target, identity, environment, and state boundary are confirmed.
• The plan or execution evidence contains no unexplained destructive action.
• Security, reliability, maintainability, and operational ownership are reviewed.
• The final result can be reproduced from version-controlled inputs.

Failure Analysis

Fix fingerprint, key, tenancy, region, provider, and IAM policy errors.

Learners isolate the smallest verified cause, correct it, rerun the relevant validation step, and record the preventive action in the course improvement log.