-
Notifications
You must be signed in to change notification settings - Fork 206
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
Adds "pattern" property for okta_user_schema and okta_user_base_schema. #159
Conversation
okta/user_schema.go
Outdated
"pattern": &schema.Schema{ | ||
Type: schema.TypeString, | ||
Optional: true, | ||
Description: "The validation pattern to use for the subschema. Must be null, '.+', or '[<pattern>]+'", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description: "The validation pattern to use for the subschema. Must be null, '.+', or '[<pattern>]+'", | |
Description: "The validation pattern to use for the subschema. Must be '.+', or '[<pattern>]+' if present.'", |
Think this might be slightly better, still not sure if we would want to clarify what the pattern
can look like.
…okta into user-schema-patterns � Conflicts: � okta/user_schema.go � sdk/user_schema_models.go
Hi @fitzoh! Thanks for the PR! I took the liberty to push some fixes regarding the |
Great, thanks @bogdanprodan-okta ! |
(At least partially) addresses https://github.com/terraform-providers/terraform-provider-okta/issues/149.
From the API docs it looks like this pattern might only be valid for the
login
property.Not sure if that's a restriction that should be enforced here.
Holding off on doc updates until I can get some feedback on how to proceed.