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

Kill gdata (again) #1656

Open
jay0lee opened this issue Aug 17, 2023 · 4 comments
Open

Kill gdata (again) #1656

jay0lee opened this issue Aug 17, 2023 · 4 comments
Assignees
Labels

Comments

@jay0lee
Copy link
Member

jay0lee commented Aug 17, 2023

gdata is currently being used by 3 APIs:

each of these is in various states of deprecation and ideally we'd remove the gdata code from GAM because it's old, crufty and may have some security issues.

In the case of Contacts API, it's been replaced with the People API. @taers232c are you aware of any use cases where Contacts API is still needed?

In the case of Email Audit API, Google Vault is meant as the much more robust replacement but the Email Audit API is still used by some customers and was never turned down. For this I suggest we drop support from the current GAM release but customers wishing to use Email Audit API calls can continue to run old versions of GAM. Should something break we can always do a patch release to that old version.

In the case of Classic sites API, afaik Classic Sites is entirely turned down: https://workspaceupdates.googleblog.com/2022/11/migrate-classic-google-sites-by-january-30-2023.html @taers232c are you aware of any further usage / need for Classic Sites API?

Once we can replace / remove these 3 APIs we can cleanup the gdata folder(s) and eliminate a lot of crufty old code.

@jay0lee jay0lee added the bug label Aug 17, 2023
@jay0lee jay0lee self-assigned this Aug 17, 2023
@jay0lee
Copy link
Member Author

jay0lee commented Aug 17, 2023

Security issues detected in old gdata / atom code. These are almost certainly benign but we should still clean them up (ideally by killing GData usage)

https://github.com/GAM-team/GAM/security/code-scanning

Also Python 3.12 seems to be taking issue with a bunch of the old regex strings in GData. See #1655

@taers232c
Copy link
Contributor

taers232c commented Aug 17, 2023 via email

@jay0lee
Copy link
Member Author

jay0lee commented Aug 18, 2023

OK, I've commited:

4454e55

which cleans up some 13,000 lines of GData cruft, mostly around tlslite and very old authentication code which GAM should never be using.

I've also added commands to our GitHub Actions testing to create/list/delete domain shared contacts so we can continue to confirm we haven't broken those commands.

@taers232c can you please test and confirm this doesn't break anything else?

@taers232c
Copy link
Contributor

taers232c commented Aug 18, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants