-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add confmap.Converter an option for ocb build manifest/template (#11584)
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds ability to add confmap.Converter as a module to build/import with ocb <!-- Issue number if applicable --> #### Link to tracking issue Fixes #11582 <!--Describe what testing was performed and which tests were added.--> #### Testing Added validation tests for pulling the converter go module in cmd/builder template/build process. Additionally, I took the default otelcorecol manifest, added a `converters` section, and added the `expandconverter` and verified that a custom collector both built, started up, and exited successfully. <!--Describe the documentation added.--> #### Documentation Changelog file added. I can also update the documentation in cmd/builder README if community thinks that is necessary. Since `confmap.Converter` is not yet registered in the OTel registry and does not have any existing components published save for the deprecated `expandconverter` I was not certain if anything further than a changelog was necessary. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Andrzej Stencel <[email protected]>
- Loading branch information
1 parent
e76145a
commit 9cc15c5
Showing
6 changed files
with
87 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: enhancement | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) | ||
component: cmd/builder | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Allow configuring `confmap.Converter` components in ocb. | ||
|
||
# One or more tracking issues or pull requests related to the change | ||
issues: [11582] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | | ||
If no converters are specified, there will be no converters added. | ||
Currently, the only published converter is `expandconverter` which is | ||
deprecated as of v0.107.0, but can still be added for testing purposes. | ||
To configure a custom converter, make sure your converter implements the converter | ||
interface and is published as a go module (or replaced locally if not published). | ||
You may then use the `converters` key in your OCB build manifest with a list of | ||
Go modules (and replaces as necessary) to include your converter. | ||
Please note that converters are order-dependent. The confmap will apply converters | ||
in order of which they are listed in your manifest if there is more than one. | ||
# Optional: The change log or logs in which this entry should be included. | ||
# e.g. '[user]' or '[user, api]' | ||
# Include 'user' if the change is relevant to end users. | ||
# Include 'api' if there is a change to a library API. | ||
# Default: '[user]' | ||
change_logs: [user] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters