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

Missing "governance" in custom role permissions #1422

Closed
L1qu1d1c3 opened this issue Jan 12, 2023 · 3 comments
Closed

Missing "governance" in custom role permissions #1422

L1qu1d1c3 opened this issue Jan 12, 2023 · 3 comments
Labels
bug enhancement Asking for new behavior or feature stale triaged Triaged into internal Jira

Comments

@L1qu1d1c3
Copy link

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

Okta's newest Access Certification feature has a new Role assignment attribute called "governance", with the options okta.governance.accessCertifications.manage and okta.governance.accessRequests.manage.

The current provider version doesn't support these two options in the "okta_admin_role_custom" resource type. Could it be added plkease

New or Affected Resource(s)

  • okta_admin_role_custom

References

@L1qu1d1c3 L1qu1d1c3 added the enhancement Asking for new behavior or feature label Jan 12, 2023
@monde
Copy link
Collaborator

monde commented Jan 17, 2023

Note to self:
Having the TF provider do input validation on this field is unnecessary and encumbers the operator to have to open issues like this when the API is updated.
okta_admin_role_custo
https://github.com/okta/terraform-provider-okta/blob/master/okta/resource_okta_admin_role_custom.go#L70-L78

@monde monde added bug triaged Triaged into internal Jira labels Jan 17, 2023
@monde
Copy link
Collaborator

monde commented Jan 17, 2023

Thanks @L1qu1d1c3 I've triaged this into our internal Jira
Okta internal reference: https://oktainc.atlassian.net/browse/OKTA-567044

@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 Mar 19, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug enhancement Asking for new behavior or feature stale triaged Triaged into internal Jira
Projects
None yet
Development

No branches or pull requests

2 participants