-
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
Add Error Reporting GAPIC as dependency #2894
Conversation
@waprin I forgot, can you assign people and add labels to PRs? |
I can't. Though my teammates could change that for me, up to you guys if you want us to. |
@waprin I gave you one-off write access to this repo. We can refactor this as a Github team if there are other Stackdriver devs we should include (especially if you need access to multiple google-cloud-* repos). FYI @jgeewax @daspecster @dhermes @tseaver @omaray @danoscarmike |
This PR is pointless unless the package actually uses the depended upon package? |
@dhermes the next incoming PR will actually use this client, but it's still not pointless, the idea is that we keep the |
Yes, that's how it's been explained to me as well, but AFAIK the generated libraries are not in the "ready to go" state yet (e.g. no docs). |
@dhermes We'll get on top of publishing GAPIC docs for all APIs in January. We also need to discuss how to integrate them with google-cloud-python docs as discussed in https://github.com/GoogleCloudPlatform/gcloud-common/issues/207. |
@dhermes @bjwatson @steren this is not remotely ready for thorough review (missing tests, docs, lots of stye issues) but I wanted to throw up the commits to give the rough sketch of adding the GAPIC as a transport for the helper API, make sure it's all LGTM to you guys and then I'll clean up the PR to merge it. This is basically what Steren and I had discussed a few weeks ago.
If you all feel good about this I'll finish up the tests/docs/style issues. Obviously not expecting any response on this until 2017, happy new year! 🎉 🎉 🎈 🎈 |
Thanks @waprin. Looks reasonable to me based on a superficial review. @lukesneeringer Can you take a more detailed look? This should have a similar structure to the Logging code that you've looked at already. |
Cool ty, will finish it up then. |
The direction LGTM. Would you mind also update the doc, so that I better understand how the end user will configure and use the module in its various variants? In general, a parameter like Will this work also allow to call, for example, the list groupStat endpoint from the module? |
@bjwatson @lukesneeringer cool ty, I wanted to ask, do we need the secure channel stuff? Is there a high level overview of that? One other problem I've run into is that Error Reporting depends on gax 0.14 but logging (which Error Reporting uses as the fallback) depends on 0.15, and @steren will try to clarify the gRPC stuff. Since we are adding the GAPIC to the module, all the autogenned VTK calls will be included as a dependency. Documentation of all those calls is still a TODO as noted above. For now this just adds the GAPIC library to this one and uses it for the handwritten helper functions. |
@waprin I believe we'll need to regenerate the GAPIC code to work with GAX The changes allow us to use @jonparrott's new google-auth library, rather than requiring the broken old oauth2client. |
@bjwatson Yes, we should regenerate the GAPIC library to use GAX 0.15.0. |
@dhermes this is ready for review |
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.
Mostly seems fine -- there are a couple spots where I need clarification (or possibly changes).
import traceback | ||
|
||
import google.cloud.logging.client | ||
try: |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
||
from google.cloud.gapic.errorreporting.v1beta1 import ( | ||
report_errors_service_client) | ||
from google.cloud.grpc.devtools.clouderrorreporting.v1beta1 import ( |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
* Add Error Reporting GAPIC as dependency This both adds the GAPIC to be used directly via this package, as well as hooking it up to the existing helpers to provide gRPC support.
…udPlatform/python-docs-samples#3698) fixes #2894 Co-authored-by: Leah E. Cole <6719667+leahecole@users.noreply.github.com>
Step 1 to resolving #2687. See that discussion thread for the other followups.
@bjwatson @dhermes