oracle / oracle/oci-cli

Missing option to set IAM group-to-role mapping (as exists in API, Console, Terraform provider)

Open
#965 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

GoldenGate
Dominant language
Python
Stars
669
Forks
236
Avg merge
1m
Merged PRs (30d)
4

Description

oci --version
3.62.2

Command oci goldengate deployment create should have --group-to-roles-mapping option but is missing. This is essential as Console use for creating GoldenGate Deployments is constrained to only selecting IAM groups from current IAM Domain (i.e. domain which was used to authenticate for Console session). That is not otherwise a limitation as GoldenGate Deployment can use groups from any IAM domain as specified by --identity-domain-id. Therefore, using another IAM Domain for GoldenGate groups/roles requires creating the GoldenGate Deployment using API or SDK.

References:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the oci goldengate deployment create command implementation and inspect how its options are mapped to the GoldenGate create request. Compare the command with the API's groupToRolesMapping attribute and Terraform's group_to_roles_mapping; done means the CLI accepts --group-to-roles-mapping and forwards it when creating a deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, cloud
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.