Skip to content
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

add schema resource and data source #20

Merged
merged 4 commits into from
Apr 9, 2021
Merged

add schema resource and data source #20

merged 4 commits into from
Apr 9, 2021

Conversation

megan07
Copy link
Contributor

@megan07 megan07 commented Apr 9, 2021

Add schema resource and data source.

Opinion question: should we call this UserSchema or leave it as Schema? The REST resource is just schemas, and I'd like to stay consistent with that. However, I think the only place this is used is with Users, the Oauth scope is userschema, and the community provider calls it gsuite_user_schema, so I could be swayed the other way.

@megan07 megan07 requested a review from appilon April 9, 2021 18:19
}

schemasService, diags := GetSchemasService(directoryService)
if len(diags) > 0 {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if len(diags) > 0 {
if diags.HasError() {

@appilon
Copy link
Contributor

appilon commented Apr 9, 2021

Just 1 minor thing

@appilon
Copy link
Contributor

appilon commented Apr 9, 2021

As for the naming thing, I would lean towards UserSchema to avoid confusion with the Terraform schema 🤷‍♂️

@megan07
Copy link
Contributor Author

megan07 commented Apr 9, 2021

Just going to note that I think I'll keep it Schema for now in case it ends up being used with resources other than User.

@megan07 megan07 merged commit dfaaf28 into main Apr 9, 2021
@megan07 megan07 deleted the megan_add_user_schema branch April 9, 2021 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants