-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[extension/googleclientauth] Add new component boilerplate scaffolding #31518
Conversation
c6ff818
to
750bd58
Compare
I tried skipping the lifecycle/shutdown tests for now in metadata.yaml and ran |
4f4e531
to
179e78f
Compare
I'm trying to run
|
I would just manually update the file with the diff |
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.
I'll defer to others, but it may be worthwhile to add a changelog for this. It looks like it's pretty common for other components to add a new_component
changelog entry for even just scaffolding 👍
3e6f71e
to
dee2c99
Compare
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.
Just some minor formatting nits. 👍 Also, I realized it might be a good time to add goleak checks to your component now, to help ensure it doesn't leak goroutines. You can simply add a package_test.go
file to your component's directory, contents could be copied from here.
Co-authored-by: Curtis Robert <crobert@splunk.com>
Co-authored-by: Curtis Robert <crobert@splunk.com>
exporters: [otlp/withauth] | ||
``` | ||
|
||
The following optional config fields are available: |
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.
Nit: It might make sense to have the options defined before the example. Not a big deal either way though. 👍
…32029) **Description:** Follow up to boilerplate PR #31518 This adds the functions calls to actually implement the extension using our downstream libraries. It also enables the shutdown tests for this extension (lifecycle tests do not seem possible for us currently) **Link to tracking Issue:** n/a **Testing:** downstream unit and integration tests, shutdown tests here **Documentation:** Here and downstream READMEs
…2442) **Description:** <Describe what has changed.> Follow up to #32029 and #31518 This marks the `googleclientauthextension` as `alpha` following the [contributing doc](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components) and [alpha stability guidelines](https://github.com/open-telemetry/opentelemetry-collector#alpha). It also adds it to `otelcontribcol` Note this also updates CONTRIBUTING.md to explain how to add the alpha component to otelcontribcol. **Link to tracking Issue:** N/A **Testing:** Downstream unit and integration tests **Documentation:** No changes except stability
Description:
This adds the basic component boilerplate following the recommendations for PR1 in https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components
Link to tracking Issue: #31412
Testing: Ran various
make ...
commands as listed in docs. Ignored generated files and failures from unrelated components.Documentation: New readme and metadata (to be filled in, see tracking issue)