[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M794448XHD7HZKNF7Z5YYZP0":3,"skill-same:01M794448XHD7HZKNF7Z5YYZP0":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M794448XHD7HZKNF7Z5YYZP0","oraclecloud-enterprise-rbac",null,"Design OCI compartment hierarchies, dynamic groups, and cross-tenancy access patterns.\nUse when planning enterprise RBAC, setting up Instance Principal auth, or debugging policy inheritance.\nTrigger with \"oraclecloud enterprise rbac\", \"oci compartments\", \"oci dynamic groups\", \"oci policy inheritance\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--oraclecloud-pack--oraclecloud-enterprise-rbac\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: oraclecloud-enterprise-rbac\ndescription: |\n  Design OCI compartment hierarchies, dynamic groups, and cross-tenancy access patterns.\n  Use when planning enterprise RBAC, setting up Instance Principal auth, or debugging policy inheritance.\n  Trigger with \"oraclecloud enterprise rbac\", \"oci compartments\", \"oci dynamic groups\", \"oci policy inheritance\".\nallowed-tools: Read, Write, Edit, Bash(pip:*), Bash(oci:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, oraclecloud, oci]\ncompatible-with: claude-code\n---\n\n# Oracle Cloud Enterprise RBAC\n\n## Overview\n\nOCI compartments are powerful but the inheritance model is confusing. Policies at root vs compartment level behave differently, dynamic groups enable compute-to-service auth without API keys, and cross-tenancy access requires matching policies on both sides. Most teams get this wrong and over-permission everything with `manage all-resources in tenancy`. This skill designs proper compartment hierarchies with least-privilege access.\n\n**Purpose:** Build a scalable, least-privilege OCI organization structure using compartments, policy inheritance, dynamic groups, and tag-based access control.\n\n## Prerequisites\n\n- **OCI Python SDK** — `pip install oci`\n- **OCI config file** at `~\u002F.oci\u002Fconfig` with valid credentials (user, fingerprint, tenancy, region, key_file)\n- **Tenancy administrator access** — compartment and policy creation requires root-level permissions\n- Familiarity with OCI IAM basics (see `oraclecloud-security-basics` for policy syntax)\n- Python 3.8+\n\n## Instructions\n\n### Step 1: Design the Compartment Hierarchy\n\nOCI compartments are nested organizational units. Unlike AWS accounts, they share a single tenancy with inherited policies. A standard enterprise layout:\n\n```\nRoot (Tenancy)\n├── shared-infra          ← DNS, networking hub, shared services\n├── security              ← Vault, audit logs, Cloud Guard\n├── dev\n│   ├── dev-compute       ← Dev instances, OKE clusters\n│   └── dev-data          ← Dev databases, object storage\n├── staging\n│   ├── staging-compute\n│   └── staging-data\n└── prod\n    ├── prod-compute\n    └── prod-data\n```\n\nCreate this hierarchy programmatically:\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\nidentity = oci.identity.IdentityClient(config)\ntenancy_id = config[\"tenancy\"]\n\ndef create_compartment(parent_id, name, description):\n    \"\"\"Create a compartment and return its OCID.\"\"\"\n    result = identity.create_compartment(\n        oci.identity.models.CreateCompartmentDetails(\n            compartment_id=parent_id,\n            name=name,\n            description=description\n        )\n    )\n    print(f\"Created: {name} ({result.data.id})\")\n    return result.data.id\n\n# Top-level compartments\nshared = create_compartment(tenancy_id, \"shared-infra\", \"Shared infrastructure services\")\nsecurity = create_compartment(tenancy_id, \"security\", \"Security and audit resources\")\ndev = create_compartment(tenancy_id, \"dev\", \"Development environment\")\nstaging = create_compartment(tenancy_id, \"staging\", \"Staging environment\")\nprod = create_compartment(tenancy_id, \"prod\", \"Production environment\")\n\n# Nested compartments\ndev_compute = create_compartment(dev, \"dev-compute\", \"Dev compute resources\")\ndev_data = create_compartment(dev, \"dev-data\", \"Dev databases and storage\")\nprod_compute = create_compartment(prod, \"prod-compute\", \"Prod compute resources\")\nprod_data = create_compartment(prod, \"prod-data\", \"Prod databases and storage\")\n```\n\n### Step 2: Understand Policy Inheritance Rules\n\nPolicy inheritance is the most misunderstood OCI concept. Three critical rules:\n\n1. **Policies at root apply to all compartments below.** A policy `Allow group DevOps to manage all-resources in tenancy` grants access everywhere.\n\n2. **Policies attached to a compartment only apply to that compartment and its children.** A policy attached to `dev` does NOT grant access to `prod`.\n\n3. **Child compartments inherit parent permissions.** If `DevOps` can `manage instance-family in compartment dev`, they can also manage instances in `dev-compute` and `dev-data` (children of `dev`).\n\n```python\n# WRONG: Attaching at root gives access everywhere\n# identity.create_policy(compartment_id=tenancy_id, statements=[\n#     \"Allow group DevOps to manage all-resources in tenancy\"  # TOO BROAD\n# ])\n\n# RIGHT: Attach policies at the appropriate compartment level\n# This policy is attached to the root but scoped to 'dev' compartment\ndev_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,  # Policies must live at root or target compartment\n        name=\"dev-team-access\",\n        description=\"Dev team full access to dev compartment only\",\n        statements=[\n            \"Allow group DevTeam to manage all-resources in compartment dev\",\n            \"Allow group DevTeam to read all-resources in compartment shared-infra\"\n        ]\n    )\n)\n\n# Prod access is separate and more restrictive\nprod_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,\n        name=\"prod-team-access\",\n        description=\"Prod team read + use, no delete\",\n        statements=[\n            \"Allow group ProdOps to use all-resources in compartment prod\",\n            \"Allow group ProdOps to read all-resources in compartment shared-infra\",\n            \"Allow group ProdOps to manage instance-family in compartment prod where request.permission != 'INSTANCE_DELETE'\"\n        ]\n    )\n)\n```\n\n### Step 3: Create Dynamic Groups for Instance Principal\n\nDynamic groups enable OCI instances and functions to authenticate to OCI services without API keys. This is the OCI equivalent of AWS IAM Roles for EC2:\n\n```python\n# Create a dynamic group matching all instances in the dev compartment\ndynamic_group = identity.create_dynamic_group(\n    oci.identity.models.CreateDynamicGroupDetails(\n        compartment_id=tenancy_id,\n        name=\"dev-instances\",\n        description=\"All compute instances in dev compartment\",\n        matching_rule=\"ANY {instance.compartment.id = 'ocid1.compartment.oc1..dev_ocid'}\"\n    )\n)\nprint(f\"Dynamic group: {dynamic_group.data.id}\")\n\n# Grant the dynamic group access to Object Storage\ndg_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,\n        name=\"dev-instances-object-storage\",\n        description=\"Let dev instances read\u002Fwrite object storage\",\n        statements=[\n            \"Allow dynamic-group dev-instances to manage object-family in compartment dev-data\"\n        ]\n    )\n)\n```\n\n**Dynamic group matching rules** support these predicates:\n- `instance.compartment.id = '\u003Cocid>'` — all instances in a compartment\n- `instance.id = '\u003Cocid>'` — specific instance\n- `tag.\u003Cnamespace>.\u003Ckey>.value = '\u003Cvalue>'` — tag-based matching\n- `ALL {rule1, rule2}` — must match all rules\n- `ANY {rule1, rule2}` — must match at least one rule\n\n### Step 4: Use Instance Principal Auth in Code\n\nInside an instance that belongs to a dynamic group, use Instance Principal instead of API keys:\n\n```python\nimport oci\n\n# On an OCI instance — no ~\u002F.oci\u002Fconfig needed\nsigner = oci.auth.signers.InstancePrincipalsSecurityTokenSigner()\nobject_storage = oci.object_storage.ObjectStorageClient({}, signer=signer)\n\n# List buckets (permissions come from dynamic group policies)\nnamespace = object_storage.get_namespace().data\nbuckets = object_storage.list_buckets(\n    namespace_name=namespace,\n    compartment_id=\"ocid1.compartment.oc1..dev_data_ocid\"\n)\nfor b in buckets.data:\n    print(f\"Bucket: {b.name}\")\n```\n\n### Step 5: Tag-Based Access Control\n\nUse defined tags for fine-grained access control across compartments:\n\n```python\n# Create a tag namespace and key for environment tagging\ntag_namespace = identity.create_tag_namespace(\n    oci.identity.models.CreateTagNamespaceDetails(\n        compartment_id=tenancy_id,\n        name=\"Operations\",\n        description=\"Operational tags for access control\"\n    )\n)\n\nidentity.create_tag(\n    tag_namespace.data.id,\n    oci.identity.models.CreateTagDetails(\n        name=\"Environment\",\n        description=\"Resource environment (dev, staging, prod)\"\n    )\n)\n\n# Policy using tag-based conditions\ntag_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,\n        name=\"tag-based-access\",\n        description=\"Access controlled by environment tags\",\n        statements=[\n            \"Allow group DevTeam to manage all-resources in tenancy where target.resource.tag.Operations.Environment = 'dev'\",\n            \"Allow group DevTeam to read all-resources in tenancy where target.resource.tag.Operations.Environment = 'prod'\"\n        ]\n    )\n)\n```\n\n## Output\n\nSuccessful completion produces:\n- A compartment hierarchy separating environments (dev\u002Fstaging\u002Fprod) and concerns (compute\u002Fdata\u002Fsecurity)\n- IAM policies attached at the correct level with least-privilege access per group\n- Dynamic groups enabling Instance Principal auth for compute instances and functions\n- Tag-based access control for cross-compartment fine-grained permissions\n\n## Error Handling\n\n| Error | Code | Cause | Solution |\n|-------|------|-------|----------|\n| NotAuthenticated | 401 | Bad config or API key | Verify `~\u002F.oci\u002Fconfig` and key_file path |\n| NotAuthorizedOrNotFound | 404 | Missing IAM policy or wrong compartment OCID | Policies must be at root for cross-compartment access |\n| InvalidParameter | 400 | Policy syntax error or invalid matching rule | Check verb, resource-type, and dynamic group rule syntax |\n| TooManyRequests | 429 | Identity API rate limit (~10 req\u002Fsec) | Back off; see `oraclecloud-rate-limits` |\n| CompartmentAlreadyExists | 409 | Duplicate compartment name in same parent | Use a unique name or reuse the existing compartment |\n| InternalError | 500 | OCI service error | Retry after 30s; check https:\u002F\u002Focistatus.oraclecloud.com |\n\n**Important:** Dynamic group changes take 5-10 minutes to propagate. If Instance Principal auth fails immediately after creating a dynamic group or policy, wait and retry.\n\n## Examples\n\n**List all compartments in a hierarchy:**\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\nidentity = oci.identity.IdentityClient(config)\n\ndef print_hierarchy(parent_id, depth=0):\n    compartments = identity.list_compartments(\n        compartment_id=parent_id,\n        lifecycle_state=\"ACTIVE\"\n    ).data\n    for c in compartments:\n        print(f\"{'  ' * depth}{c.name} ({c.id})\")\n        print_hierarchy(c.id, depth + 1)\n\nprint_hierarchy(config[\"tenancy\"])\n```\n\n**Quick audit of all dynamic groups:**\n\n```bash\noci iam dynamic-group list --compartment-id \u003Ctenancy-ocid> --all \\\n  --query \"data[].{name:name, rule:\\\"matching-rule\\\"}\" --output table\n```\n\n## Resources\n\n- [Compartment Management](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FIdentity\u002FTasks\u002Fmanagingcompartments.htm) — creating and organizing compartments\n- [Policy Inheritance](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FIdentity\u002FConcepts\u002Fpolicies.htm) — how policies inherit through the compartment tree\n- [Dynamic Groups](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FIdentity\u002FTasks\u002Fmanagingdynamicgroups.htm) — matching rules and Instance Principal\n- [Tag-Based Access Control](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FTagging\u002FTasks\u002Fmanagingaccesswithtags.htm) — using defined tags in policies\n- [Python SDK Reference](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002Ftools\u002Fpython\u002Flatest\u002F) — IdentityClient API\n\n## Next Steps\n\nAfter the compartment hierarchy is in place, see `oraclecloud-multi-env-setup` for profile-based environment switching, or `oraclecloud-security-basics` for IAM policy syntax fundamentals.\n","# Oracle Cloud Enterprise RBAC\n\n## Overview\n\nOCI compartments are powerful but the inheritance model is confusing. Policies at root vs compartment level behave differently, dynamic groups enable compute-to-service auth without API keys, and cross-tenancy access requires matching policies on both sides. Most teams get this wrong and over-permission everything with `manage all-resources in tenancy`. This skill designs proper compartment hierarchies with least-privilege access.\n\n**Purpose:** Build a scalable, least-privilege OCI organization structure using compartments, policy inheritance, dynamic groups, and tag-based access control.\n\n## Prerequisites\n\n- **OCI Python SDK** — `pip install oci`\n- **OCI config file** at `~\u002F.oci\u002Fconfig` with valid credentials (user, fingerprint, tenancy, region, key_file)\n- **Tenancy administrator access** — compartment and policy creation requires root-level permissions\n- Familiarity with OCI IAM basics (see `oraclecloud-security-basics` for policy syntax)\n- Python 3.8+\n\n## Instructions\n\n### Step 1: Design the Compartment Hierarchy\n\nOCI compartments are nested organizational units. Unlike AWS accounts, they share a single tenancy with inherited policies. A standard enterprise layout:\n\n```\nRoot (Tenancy)\n├── shared-infra          ← DNS, networking hub, shared services\n├── security              ← Vault, audit logs, Cloud Guard\n├── dev\n│   ├── dev-compute       ← Dev instances, OKE clusters\n│   └── dev-data          ← Dev databases, object storage\n├── staging\n│   ├── staging-compute\n│   └── staging-data\n└── prod\n    ├── prod-compute\n    └── prod-data\n```\n\nCreate this hierarchy programmatically:\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\nidentity = oci.identity.IdentityClient(config)\ntenancy_id = config[\"tenancy\"]\n\ndef create_compartment(parent_id, name, description):\n    \"\"\"Create a compartment and return its OCID.\"\"\"\n    result = identity.create_compartment(\n        oci.identity.models.CreateCompartmentDetails(\n            compartment_id=parent_id,\n            name=name,\n            description=description\n        )\n    )\n    print(f\"Created: {name} ({result.data.id})\")\n    return result.data.id\n\n# Top-level compartments\nshared = create_compartment(tenancy_id, \"shared-infra\", \"Shared infrastructure services\")\nsecurity = create_compartment(tenancy_id, \"security\", \"Security and audit resources\")\ndev = create_compartment(tenancy_id, \"dev\", \"Development environment\")\nstaging = create_compartment(tenancy_id, \"staging\", \"Staging environment\")\nprod = create_compartment(tenancy_id, \"prod\", \"Production environment\")\n\n# Nested compartments\ndev_compute = create_compartment(dev, \"dev-compute\", \"Dev compute resources\")\ndev_data = create_compartment(dev, \"dev-data\", \"Dev databases and storage\")\nprod_compute = create_compartment(prod, \"prod-compute\", \"Prod compute resources\")\nprod_data = create_compartment(prod, \"prod-data\", \"Prod databases and storage\")\n```\n\n### Step 2: Understand Policy Inheritance Rules\n\nPolicy inheritance is the most misunderstood OCI concept. Three critical rules:\n\n1. **Policies at root apply to all compartments below.** A policy `Allow group DevOps to manage all-resources in tenancy` grants access everywhere.\n\n2. **Policies attached to a compartment only apply to that compartment and its children.** A policy attached to `dev` does NOT grant access to `prod`.\n\n3. **Child compartments inherit parent permissions.** If `DevOps` can `manage instance-family in compartment dev`, they can also manage instances in `dev-compute` and `dev-data` (children of `dev`).\n\n```python\n# WRONG: Attaching at root gives access everywhere\n# identity.create_policy(compartment_id=tenancy_id, statements=[\n#     \"Allow group DevOps to manage all-resources in tenancy\"  # TOO BROAD\n# ])\n\n# RIGHT: Attach policies at the appropriate compartment level\n# This policy is attached to the root but scoped to 'dev' compartment\ndev_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,  # Policies must live at root or target compartment\n        name=\"dev-team-access\",\n        description=\"Dev team full access to dev compartment only\",\n        statements=[\n            \"Allow group DevTeam to manage all-resources in compartment dev\",\n            \"Allow group DevTeam to read all-resources in compartment shared-infra\"\n        ]\n    )\n)\n\n# Prod access is separate and more restrictive\nprod_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,\n        name=\"prod-team-access\",\n        description=\"Prod team read + use, no delete\",\n        statements=[\n            \"Allow group ProdOps to use all-resources in compartment prod\",\n            \"Allow group ProdOps to read all-resources in compartment shared-infra\",\n            \"Allow group ProdOps to manage instance-family in compartment prod where request.permission != 'INSTANCE_DELETE'\"\n        ]\n    )\n)\n```\n\n### Step 3: Create Dynamic Groups for Instance Principal\n\nDynamic groups enable OCI instances and functions to authenticate to OCI services without API keys. This is the OCI equivalent of AWS IAM Roles for EC2:\n\n```python\n# Create a dynamic group matching all instances in the dev compartment\ndynamic_group = identity.create_dynamic_group(\n    oci.identity.models.CreateDynamicGroupDetails(\n        compartment_id=tenancy_id,\n        name=\"dev-instances\",\n        description=\"All compute instances in dev compartment\",\n        matching_rule=\"ANY {instance.compartment.id = 'ocid1.compartment.oc1..dev_ocid'}\"\n    )\n)\nprint(f\"Dynamic group: {dynamic_group.data.id}\")\n\n# Grant the dynamic group access to Object Storage\ndg_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,\n        name=\"dev-instances-object-storage\",\n        description=\"Let dev instances read\u002Fwrite object storage\",\n        statements=[\n            \"Allow dynamic-group dev-instances to manage object-family in compartment dev-data\"\n        ]\n    )\n)\n```\n\n**Dynamic group matching rules** support these predicates:\n- `instance.compartment.id = '\u003Cocid>'` — all instances in a compartment\n- `instance.id = '\u003Cocid>'` — specific instance\n- `tag.\u003Cnamespace>.\u003Ckey>.value = '\u003Cvalue>'` — tag-based matching\n- `ALL {rule1, rule2}` — must match all rules\n- `ANY {rule1, rule2}` — must match at least one rule\n\n### Step 4: Use Instance Principal Auth in Code\n\nInside an instance that belongs to a dynamic group, use Instance Principal instead of API keys:\n\n```python\nimport oci\n\n# On an OCI instance — no ~\u002F.oci\u002Fconfig needed\nsigner = oci.auth.signers.InstancePrincipalsSecurityTokenSigner()\nobject_storage = oci.object_storage.ObjectStorageClient({}, signer=signer)\n\n# List buckets (permissions come from dynamic group policies)\nnamespace = object_storage.get_namespace().data\nbuckets = object_storage.list_buckets(\n    namespace_name=namespace,\n    compartment_id=\"ocid1.compartment.oc1..dev_data_ocid\"\n)\nfor b in buckets.data:\n    print(f\"Bucket: {b.name}\")\n```\n\n### Step 5: Tag-Based Access Control\n\nUse defined tags for fine-grained access control across compartments:\n\n```python\n# Create a tag namespace and key for environment tagging\ntag_namespace = identity.create_tag_namespace(\n    oci.identity.models.CreateTagNamespaceDetails(\n        compartment_id=tenancy_id,\n        name=\"Operations\",\n        description=\"Operational tags for access control\"\n    )\n)\n\nidentity.create_tag(\n    tag_namespace.data.id,\n    oci.identity.models.CreateTagDetails(\n        name=\"Environment\",\n        description=\"Resource environment (dev, staging, prod)\"\n    )\n)\n\n# Policy using tag-based conditions\ntag_policy = identity.create_policy(\n    oci.identity.models.CreatePolicyDetails(\n        compartment_id=tenancy_id,\n        name=\"tag-based-access\",\n        description=\"Access controlled by environment tags\",\n        statements=[\n            \"Allow group DevTeam to manage all-resources in tenancy where target.resource.tag.Operations.Environment = 'dev'\",\n            \"Allow group DevTeam to read all-resources in tenancy where target.resource.tag.Operations.Environment = 'prod'\"\n        ]\n    )\n)\n```\n\n## Output\n\nSuccessful completion produces:\n- A compartment hierarchy separating environments (dev\u002Fstaging\u002Fprod) and concerns (compute\u002Fdata\u002Fsecurity)\n- IAM policies attached at the correct level with least-privilege access per group\n- Dynamic groups enabling Instance Principal auth for compute instances and functions\n- Tag-based access control for cross-compartment fine-grained permissions\n\n## Error Handling\n\n| Error | Code | Cause | Solution |\n|-------|------|-------|----------|\n| NotAuthenticated | 401 | Bad config or API key | Verify `~\u002F.oci\u002Fconfig` and key_file path |\n| NotAuthorizedOrNotFound | 404 | Missing IAM policy or wrong compartment OCID | Policies must be at root for cross-compartment access |\n| InvalidParameter | 400 | Policy syntax error or invalid matching rule | Check verb, resource-type, and dynamic group rule syntax |\n| TooManyRequests | 429 | Identity API rate limit (~10 req\u002Fsec) | Back off; see `oraclecloud-rate-limits` |\n| CompartmentAlreadyExists | 409 | Duplicate compartment name in same parent | Use a unique name or reuse the existing compartment |\n| InternalError | 500 | OCI service error | Retry after 30s; check https:\u002F\u002Focistatus.oraclecloud.com |\n\n**Important:** Dynamic group changes take 5-10 minutes to propagate. If Instance Principal auth fails immediately after creating a dynamic group or policy, wait and retry.\n\n## Examples\n\n**List all compartments in a hierarchy:**\n\n```python\nimport oci\n\nconfig = oci.config.from_file(\"~\u002F.oci\u002Fconfig\")\nidentity = oci.identity.IdentityClient(config)\n\ndef print_hierarchy(parent_id, depth=0):\n    compartments = identity.list_compartments(\n        compartment_id=parent_id,\n        lifecycle_state=\"ACTIVE\"\n    ).data\n    for c in compartments:\n        print(f\"{'  ' * depth}{c.name} ({c.id})\")\n        print_hierarchy(c.id, depth + 1)\n\nprint_hierarchy(config[\"tenancy\"])\n```\n\n**Quick audit of all dynamic groups:**\n\n```bash\noci iam dynamic-group list --compartment-id \u003Ctenancy-ocid> --all \\\n  --query \"data[].{name:name, rule:\\\"matching-rule\\\"}\" --output table\n```\n\n## Resources\n\n- [Compartment Management](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FIdentity\u002FTasks\u002Fmanagingcompartments.htm) — creating and organizing compartments\n- [Policy Inheritance](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FIdentity\u002FConcepts\u002Fpolicies.htm) — how policies inherit through the compartment tree\n- [Dynamic Groups](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FIdentity\u002FTasks\u002Fmanagingdynamicgroups.htm) — matching rules and Instance Principal\n- [Tag-Based Access Control](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002FContent\u002FTagging\u002FTasks\u002Fmanagingaccesswithtags.htm) — using defined tags in policies\n- [Python SDK Reference](https:\u002F\u002Fdocs.oracle.com\u002Fen-us\u002Fiaas\u002Ftools\u002Fpython\u002Flatest\u002F) — IdentityClient API\n\n## Next Steps\n\nAfter the compartment hierarchy is in place, see `oraclecloud-multi-env-setup` for profile-based environment switching, or `oraclecloud-security-basics` for IAM policy syntax fundamentals.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","oraclecloud","oci","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Design OCI compartment hierarchies, dynamic groups, and cross-tenancy access patterns.\nUse when planning enterprise RBAC, setting up Instance Principal auth, or debugging policy inheritance.\nTrigger with \"oraclecloud enterprise rbac\", \"oci compartments\", \"oci dynamic groups\", \"oci policy inheritance\".\n","Read, Write, Edit, Bash(pip:*), Bash(oci:*), Grep","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--oraclecloud-pack--oraclecloud-enterprise-rbac",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill oraclecloud-enterprise-rbac",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill oraclecloud-enterprise-rbac",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill oraclecloud-enterprise-rbac","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--oraclecloud-pack--oraclecloud-enterprise-rbac\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]