Skip to content

Conversation

@pjanotti
Copy link
Contributor

@pjanotti pjanotti commented Jul 9, 2020

This zipkin fork contains a workaround for a version of Envoy that generates incorrect json payload to Zipkin. This is not intended to be merged on master since Envoy already fixed the issue, this is just a test for the workaround on top of v0.5.0.

This zipkin fork contains a workaround for a version of Envoy that generates incorrect json payload to Zipkin. This is not intended to be merged on master since Envoy already fixed the issue, this is just a temporary workaround for this branch.
@codecov
Copy link

codecov bot commented Jul 9, 2020

Codecov Report

Merging #1302 into release/v0.5.x will decrease coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@                Coverage Diff                 @@
##           release/v0.5.x    #1302      +/-   ##
==================================================
- Coverage           88.54%   88.51%   -0.03%     
==================================================
  Files                 207      207              
  Lines               14945    14945              
==================================================
- Hits                13233    13229       -4     
- Misses               1283     1285       +2     
- Partials              429      431       +2     
Impacted Files Coverage Δ
translator/internaldata/resource_to_oc.go 86.04% <0.00%> (-4.66%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c78701f...46a391a. Read the comment docs.

@pjanotti pjanotti closed this Jul 9, 2020
@pjanotti pjanotti deleted the not-2-merge-use-zipkin-fork-test branch March 8, 2021 20:15
hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this pull request Apr 27, 2023
…y#1302)

Bumps [boto3](https://github.com/boto/boto3) from 1.21.7 to 1.21.8.
- [Release notes](https://github.com/boto/boto3/releases)
- [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst)
- [Commits](boto/boto3@1.21.7...1.21.8)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
swiatekm pushed a commit to swiatekm/opentelemetry-collector that referenced this pull request Oct 9, 2024
)

* Enable external configmap checksum

Fixes [collector] No collector reload when using external configmap open-telemetry#1194

* Update examples for `opentelemetry-collector`

* Rename option to `configFile` for better consistency

* Template checksum annotation for all Deployment modes

* Add example for external configmap

* Hint with option name that config is a chart Template

* Remove unneeded example

* Adhere to existing user-config convention

* Update Collector chart schema to include new property

* Regenerate Collector examples

* Revert "Regenerate Collector examples"

This reverts commit 5e6d8f885e46dc1e74ef2bd312c75d1e3c0fca89.

* Remove configmap from local testing

* Generate annotation checksums by inferring ConfigMap name from the value of `existingName`

* Remove configmap from local testing

* Run `make generate-examples CHARTS=opentelemetry-collector`

* Bring back `configMap.existingPath` option

There doesn't seem to be a way to get at rendered template contents in Helm. This key allows a user to specify the path to template file that will be used to create `configMap.existingName`, in cases like mine where we want to wrap this chart in a chart that feeds in custom configmap contents.

* Regen examples to match upstream

* Improve comments based on PR comments

* Bump chart

* Update examples for chart version `102.1`

* Prefer `SHOULD`

Co-authored-by: Tyler Helmuth <[email protected]>

---------

Co-authored-by: Tyler Helmuth <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant