-
Notifications
You must be signed in to change notification settings - Fork 207
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
Feat free form expression #1027
Conversation
…string for data_source_okta_user and data_source_okta_users
I think we'd have to update the docs as well right?
Arguments Reference
|
@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 |
b4e97d8
to
bcf7615
Compare
Co-authored-by: Christian Bargmann <chris@cbrgm.net>
bcf7615
to
b7e756e
Compare
Awesome! Thanks for your great work! Really cool to see this is happening! |
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
anddata_source_okta_users
as discussed in #1010 .Usage example:
This allows more flexible search parameters for the datasources mentioned above.
Also, adds
compound_search_operator
property to data sourceokta_user
andokta_users
that is used to join multiple search elements. Previously it was a hard codedAND
operation.