You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 other comments that do not add relevant new information or questions, 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
There is a new EA feature Permission conditions It would be nice to have support for this in the TF provider 🙂
As a side note:
Its there currently an exception around when to expect provider support for new okta features?
A statement like the following wouldn't commit the team to an SLA but would still be beneficial (imo) to set expectations and may prevent issue like this one for things that the provider team may already be working on
"The Terraform provider team does not support new Okta features until they are generally available and available in the API. The work to add feature support to the terraform provider is always subject to prioritisation and availability"
New or Affected Resource(s)
okta_admin_role_custom
Potential Terraform Configuration
resource"okta_admin_role_custom""limited_readonly" {
label="limited readOnly"description="readOnly access to apps, groups, and a subset of user profile attributes"permissions=[
"okta.users.read",
"okta.groups.read",
"okta.apps.read",
]
conditions {
permission="okta.users.read"include=[
"firstName",
"lastName",
"login",
"email",
"mobilePhone"
]
exclude=[]
}
}
References
#0000
The text was updated successfully, but these errors were encountered:
Community Note
Description
There is a new EA feature Permission conditions It would be nice to have support for this in the TF provider 🙂
As a side note:
Its there currently an exception around when to expect provider support for new okta features?
A statement like the following wouldn't commit the team to an SLA but would still be beneficial (imo) to set expectations and may prevent issue like this one for things that the provider team may already be working on
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: