Consistency - align datasource_okta_group(s) `search` schema with datasource_okta_user(s)

[exitcode0]

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

userSearchSchemaDescription is (imo) better than having raw access to the search string because it support the dynamic meta argument

I'd like to request that we align the datasource_okta_group(s) resources with this implementation

I'd like to ask about if a change like this would require a deprecation or other change management as it would change the schema and the expected value quite a bit Would something like this have to wait for a V5 release? Does the Okta provider team have any target dates for a V5 release? Is the team happy to cut new major versions as and when the requirement comes up?

New or Affected Resource(s)

• dataSource_okta_group
• dataSource_okta_groups

Potential Terraform Configuration

data "okta_groups" "this" {
  type                     = "OKTA_GROUP"
  compound_search_operator = "or"

  dynamic "search" {
    for_each = [
      "123",
      "456"
    ]
    content {
      name       = "id"
      comparison = "eq"
      value      = search.value
    }
  }
}

References

• #0000

[duytiennguyen-okta]

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