-
Notifications
You must be signed in to change notification settings - Fork 553
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
fix(okta_auth_backend_group): allow '/' in group_name #687
fix(okta_auth_backend_group): allow '/' in group_name #687
Conversation
Hi! Thanks for working on this! My guess is that the main reason we don't allow "/" in various path-related parameters is because at times, the code needs to find out which path a particular mount of a back end is at. It's easier to figure out when you don't need to worry about extra slashes. In our contribution guidelines, we ask for test coverage before we review PR's. Would you be willing to add tests covering all fields changed where a "/" is now allowable, and make sure they still come out with the correct mount paths? Also, the docs may need to be updated (I'm not sure). Happy to circle back and give a review when that's done. Thanks again! |
@tyrannosaurus-becks ok 👌 I will work on it |
53ee7da
to
9872f84
Compare
@tyrannosaurus-becks I have updated the PR.
If it fits the need I will replicate this model to TestAccOktaAuthBackendUser and TestAccOktaAuthBackend Let me know about it ;) |
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.
This looks great! Thank you so much!
* fix(okta_auth_backend_group): allow '/' in group_name * refacto(okta): test names to be compliant with TF standard * refacto(okta): tests - factorize organization parameter * feat(okta): add test for group names with '/' inside
Community Note
Maybe I missed some context but why do we not allowed '/' initially in the group name ?
Release note for CHANGELOG:
Output from acceptance testing: