Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for new EA feature - Custom role "permission conditions" #1571

Open
exitcode0 opened this issue May 25, 2023 · 3 comments · May be fixed by #2077
Open

Support for new EA feature - Custom role "permission conditions" #1571

exitcode0 opened this issue May 25, 2023 · 3 comments · May be fixed by #2077
Labels
enhancement Asking for new behavior or feature no-stalebot triaged Triaged into internal Jira

Comments

@exitcode0
Copy link
Contributor

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 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
@exitcode0 exitcode0 added the enhancement Asking for new behavior or feature label May 25, 2023
@duytiennguyen-okta duytiennguyen-okta added triaged Triaged into internal Jira and removed triaged Triaged into internal Jira labels May 30, 2023
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the stale label Jul 30, 2023
@exitcode0
Copy link
Contributor Author

Not Stale :)

@duytiennguyen-okta
Copy link
Contributor

OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-712701

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Asking for new behavior or feature no-stalebot triaged Triaged into internal Jira
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants