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

Remove Debugger directory in light of end-of-support in May 2023 #6153

Open
shreejad opened this issue May 2, 2023 · 3 comments
Open

Remove Debugger directory in light of end-of-support in May 2023 #6153

shreejad opened this issue May 2, 2023 · 3 comments
Assignees
Labels
api: clouddebugger Issues related to the Cloud Debugger API. eol End of life. Deprecating support for a previous version. priority: p2 Moderately-important priority. Fix may not be included in next release.

Comments

@shreejad
Copy link

shreejad commented May 2, 2023

Cloud Debugger has been deprecated since May 2022 - https://cloud.google.com/debugger/docs/release-notes?authuser=1#May_16_2022
End of support is in 30 days - May 31, 2023.

In light of this, is there a plan to remove the following directory?
https://github.com/googleapis/google-cloud-php/tree/main/Debugger

Current PHP Debugger docs - https://cloud.google.com/debugger/docs/setup/php#gae-flex

I'm part of the GAE team, so trying to understand how Flex customers will be impacted.

@ajupazhamayil ajupazhamayil added api: clouddebugger Issues related to the Cloud Debugger API. eol End of life. Deprecating support for a previous version. priority: p2 Moderately-important priority. Fix may not be included in next release. labels May 10, 2023
@bshaffer bshaffer self-assigned this May 16, 2023
@bshaffer
Copy link
Contributor

Thank you @shreejad. We can mark the package as abandoned, and stop generating documentation/client libraries for it. However, where should we direct users who are looking for a library to migrate to?

@bshaffer
Copy link
Contributor

After discussion with the Cloud Debugger team, here is the course of action:

  1. Add the Firebase connection, which will allow users to move to Firebase when the debugger API is deactivated (and use snapshot-debugger instead) and cut a release as soon as possible.
  2. By 31 May, mark all Debugger classes and README as deprecated. Remove generated code updates (owlbot)
  3. After 31 August, mark the package as "abandoned" in composer, delete the content, and leave a README with instructions on how to fork the repo with the code intact.
@shreejad
Copy link
Author

Thanks for the followup, and co-ordinating with the Debugger team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: clouddebugger Issues related to the Cloud Debugger API. eol End of life. Deprecating support for a previous version. priority: p2 Moderately-important priority. Fix may not be included in next release.
3 participants