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

[Microsoft Graph v1.0]: aad siteclassification set #2677

Closed
garrytrinder opened this issue Sep 4, 2021 · 5 comments
Closed

[Microsoft Graph v1.0]: aad siteclassification set #2677

garrytrinder opened this issue Sep 4, 2021 · 5 comments

Comments

@garrytrinder
Copy link
Member

The aad siteclassification set command currently uses the beta/settings endpoint in its implementation, this should be updated to use the v1.0/groupSettings endpoint.

const requestOptions: any = {
url: `${this.resource}/beta/settings`,
headers: {
accept: 'application/json;odata.metadata=none'
},
responseType: 'json'
};

Note: The /beta version of this API is only applies to groups. The /v1.0 version of this API has been renamed to Get groupSetting.

beta docs: https://docs.microsoft.com/en-us/graph/api/directorysetting-get?view=graph-rest-beta&tabs=http
v1.0 docs: https://docs.microsoft.com/en-us/graph/api/resources/groupsetting?view=graph-rest-1.0&tabs=http

const requestOptions: any = {
url: `${this.resource}/beta/settings/${unifiedGroupSetting[0].id}`,
headers: {
accept: 'application/json;odata.metadata=none',
'content-type': 'application/json'
},
responseType: 'json',
data: updatedDirSettings
};

Note: The /beta version of this API only applies to groups. The /v1.0 version of this API has been renamed to Update groupSettings.

beta docs: https://docs.microsoft.com/en-us/graph/api/directorysetting-update?view=graph-rest-beta&tabs=http
v1.0 docs: https://docs.microsoft.com/en-us/graph/api/groupsetting-update?view=graph-rest-1.0&tabs=http

@Atharva321
Copy link
Contributor

Hii, I am interested to work on this issue.

@Atharva321
Copy link
Contributor

will only changing endpoint on line no. 43 and 132 fix the issue?

@garrytrinder
Copy link
Member Author

Thank you for your help @Atharva321 👍

We should also remove the attention remark in the corresponding documentation page and update the requests in the corresponding tests to reflect the change from using the beta endpoint to the v1.0 endpoint.

@Atharva321
Copy link
Contributor

Hii, Done the PR . Plz any other changes need to be done or its fine?

@waldekmastykarz
Copy link
Member

Thank you! We'll review the PR shortly

@waldekmastykarz waldekmastykarz added this to the v4.1 milestone Oct 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants