5.x: OKE provisioning on sub-compartment which has no direct policy permission at the tenancy level #768
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
The aim of this request is to be able to use this terraform module under a sub-compartment hierarchy which the provisioner has the full admin policies, but not at the root tenancy/compartment level.
Moreover, we should be able to leverage usage of an alternative identity domain for dynamic-group and service account users that are at the top level of this sub-compartment hierarchy.
New or Affected Resource(s)
I'm targeting the 5.x development branch.
affected terraform inner-modules are:
- iam