oraclecloud-multi-env-setup

Featured

Configure multi-environment OCI workflows with config profiles and compartment-per-environment patterns. Use when setting up dev/staging/prod separation, switching between OCI profiles, or preventing accidental production deployments. Trigger with "oraclecloud multi env setup", "oci profiles", "oci environments", "oci config profiles".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Oracle Cloud Multi-Environment Setup ## Overview OCI has no "accounts" like AWS — you use compartments plus OCI config profiles for dev/staging/prod separation. But profile switching is manual, compartment OCIDs are easy to confuse, and one wrong `--compartment-id` deploys to production. This skill sets up safe multi-environment workflows with named profiles, compartment aliasing, environment validation, and deployment guardrails. **Purpose:** Configure safe, repeatable multi-environment OCI workflows that prevent accidental cross-environment operations. ## Prerequisites - **OCI Python SDK** — `pip install oci` - **OCI CLI** — installed and configured (`oci setup config`) - **Separate API keys per environment** (recommended) or a single key with cross-compartment policies - **Compartment OCIDs** for each environment (dev, staging, prod) - Python 3.8+ ## Instructions ### Step 1: Configure Multi-Profile ~/.oci/config The OCI config file supports named profiles. Each profile can point to different tenancies, regions, or use different API keys: ```ini # ~/.oci/config [DEFAULT] user=ocid1.user.oc1..exampleuniqueID fingerprint=aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99 tenancy=ocid1.tenancy.oc1..exampleuniqueID region=us-ashburn-1 key_file=~/.oci/oci_api_key.pem [DEV] user=ocid1.user.oc1..exampleuniqueID fingerprint=aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99 tenancy=ocid1.tenancy.oc1..exampleuniqueID region=us-ashburn-1 key_file=~/.oci/oci_api_key_dev.pem [S...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Anthropic · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

oraclecloud-local-dev-loop

Set up a productive local OCI development workflow using CLI and SDK instead of the web console. Use when the OCI Console is too slow, setting up CLI profiles, or building shell aliases for common operations. Trigger with "oci local dev", "oci cli setup", "oraclecloud dev workflow", "avoid oci console".

2,266 Updated today
jeremylongshore
AI & Automation Featured

oraclecloud-enterprise-rbac

Design OCI compartment hierarchies, dynamic groups, and cross-tenancy access patterns. Use when planning enterprise RBAC, setting up Instance Principal auth, or debugging policy inheritance. Trigger with "oraclecloud enterprise rbac", "oci compartments", "oci dynamic groups", "oci policy inheritance".

2,266 Updated today
jeremylongshore
AI & Automation Featured

oraclecloud-prod-checklist

Pre-production readiness checklist for OCI — backup policies, security audit, key rotation, encryption, and Cloud Guard. Use when preparing an OCI environment for production workloads or auditing an existing deployment. Trigger with "oraclecloud prod checklist", "oci production ready", "oci security audit", "oci well-architected".

2,266 Updated today
jeremylongshore
AI & Automation Featured

customerio-multi-env-setup

Configure Customer.io multi-environment setup with workspace isolation. Use when setting up dev/staging/prod workspaces, environment-aware clients, or Kubernetes config overlays. Trigger: "customer.io environments", "customer.io staging", "customer.io dev prod", "customer.io workspace isolation".

2,266 Updated today
jeremylongshore
AI & Automation Featured

databricks-multi-env-setup

Configure Databricks across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Databricks configurations. Trigger with phrases like "databricks environments", "databricks staging", "databricks dev prod", "databricks environment setup", "databricks config by env".

2,266 Updated today
jeremylongshore