-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Merge 'logging-api' branch to master. #1685
Conversation
Squashed after review on PR #1488.
- Copyright year -> 2016. - Pubsub -> Logging. - Other formatting issues from @dhermes' review.
Addresses: #1564 (comment)
…otobf Hide 'six' and 'google.protobuf' from pylint's borked import sniffing.
Add 'Logger.log_text' method.
Add 'Logger.log_struct'
Add 'Logger.delete' method.
Add 'Client.list_entries'.
Add 'Logger.list_entries'.
Add 'Sink.create' API wrapper and 'Client.sink' factory.
Add 'Sink.exists' API wrapper.
Add 'Sink.reload' API wrapper.
Labels can be passed in explicitly to the 'log_text', 'log_struct', or 'log_proto' methods. If not passed, any default values configured on the logger instance will be used. See: #1566.
It was needed earlier for batch support, but was masked by the attribute on the mock '_Logger' used by the batch tests.
Support entry labels
Parse from API resource if found.
- insert_id - severity - http_request See: #1566.
…severity_httprequest Add support for logging w/ per-request metadata.
Fixes order-based failure between 'log_struct' and 'log_test'. #1657 still breaks the teardown.
Uses the Bigquery destination because that one runs quickest.
…ing_logger_name Avoid reusing logger name in logging system tests
Add system test for 'Sink.reload'.
Add system test for 'Sink.update'.
…data Add system tests for logging w/ insert_id/severty/http_request metdata.
…ting_logs Add exponential backoff for deletion failures.
…e_pubsub_topic Add system test for 'Sink.create' using a Pubsub topic
@tseaver Anything for me to do here? Also, any idea what triggered AppVeyor? |
@dhermes I don't think further review is really needed: each of the commits on the branch are the result of reviewed PRs. I know there will be a (small) conflict with your @jgeewax I plan to merge tomorrow, if that doesn't conflict with anything else planned for the day. |
No description provided.