Feat free form expression

[monde]

Okta controlled branch of @cbrgm's work in #1013:

This PR adds a free form expression string as an alternative search criteria to data_source_okta_user and data_source_okta_users as discussed in #1010 .

Usage example:

data "okta_users" "foo" {
  search {
    expression = "profile.department eq \"Engineering\" and (created lt \"2014-01-01T00:00:00.000Z\" or status eq \"ACTIVE\")"
  }
}

This allows more flexible search parameters for the datasources mentioned above.

Also, adds compound_search_operator property to data source okta_user and okta_users that is used to join multiple search elements. Previously it was a hard coded AND operation.

[cbrgm]

I think we'd have to update the docs as well right?

data "okta_users" "example" {

  compound_search_operator = "or"

  search {
    name       = "profile.department"
    value      = "Engineering"
    comparison = "eq"
  }

  search {
    name       = "profile.department"
    value      = "Data Analytics"
    comparison = "eq"
  }
}

Arguments Reference

• ...
• compound_search_operator - (Optional) Search operator uses when joining mulitple search clauses.

[monde]

I think we'd have to update the docs as well right?

@cbrgm agreed. I put the PR into draft status as I had to turn my attention to another matter at Okta. Also, I got blocked on trying to make ConflictsWith work correctly in the schema (expression conflicts with name/value/comparison, and visa versa). I'll put some more polish into this PR.

[monde]

@cbrgm this is released as v3.23.0

[cbrgm]

Awesome! Thanks for your great work! Really cool to see this is happening!