-
Notifications
You must be signed in to change notification settings - Fork 55
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
chore!: deprecate AppEngineHandler and ContainerEngineHandler #298
Changes from all commits
455f8c0
f6f70af
761a4c0
cf789ed
f6cb335
c6b2b05
a7bec22
d62c421
0b8ecde
6ce4b9e
6aea173
7b77ef0
a5f6a90
5576128
db7c131
cc476fa
516ab17
bba5737
41892af
a88f43c
935fdb8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
Structured Log Handler | ||
==================================== | ||
|
||
.. automodule:: google.cloud.logging_v2.handlers.structured_log | ||
:members: | ||
:show-inheritance: |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,8 +35,6 @@ | |
from google.cloud.logging_v2._http import _MetricsAPI as JSONMetricsAPI | ||
from google.cloud.logging_v2._http import _SinksAPI as JSONSinksAPI | ||
from google.cloud.logging_v2.handlers import CloudLoggingHandler | ||
from google.cloud.logging_v2.handlers import AppEngineHandler | ||
from google.cloud.logging_v2.handlers import ContainerEngineHandler | ||
from google.cloud.logging_v2.handlers import StructuredLogHandler | ||
from google.cloud.logging_v2.handlers import setup_logging | ||
from google.cloud.logging_v2.handlers.handlers import EXCLUDED_LOGGER_DEFAULTS | ||
|
@@ -352,9 +350,9 @@ def get_default_handler(self, **kw): | |
|
||
if isinstance(monitored_resource, Resource): | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @daniel-sanche is it possible to document the behavior of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I added this suggestion to the open issue around updating the docs for v3. Let me know if you have thoughts about whether docs should be updated along with each change, or as a pass at the end of the milestone |
||
if monitored_resource.type == _GAE_RESOURCE_TYPE: | ||
return AppEngineHandler(self, **kw) | ||
CloudLoggingHandler(self, resource=monitored_resource, **kw) | ||
elif monitored_resource.type == _GKE_RESOURCE_TYPE: | ||
return ContainerEngineHandler(**kw) | ||
return StructuredLogHandler(**kw, project_id=self.project) | ||
elif ( | ||
monitored_resource.type == _GCF_RESOURCE_TYPE | ||
and sys.version_info[0] == 3 | ||
|
This file was deleted.
This file was deleted.
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.
We should mark the classes as deprecated: update the docs to mention that they are not returned anymore and that new classes replace them. Folks who have existing code using 2.* library release should have a path forward that explains how to upgrade to 3.0.0
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.
My plan was to go through and update the docs at the end of the milestone, just in case any docs changes become out of date later (#245)
Do you think that makes sense, or should I try to update the docs along-side changes?
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.
We can update the docs later. The point here is more about the annotation of the classes.