AlinsRan opened a new pull request, #2889:
URL: https://github.com/apache/apisix-ingress-controller/pull/2889
### Description
Bumps the OpenTelemetry Go modules from `v1.44.0` to `v1.45.0`, clearing the
three open Dependabot alerts on this repository. All three alerts point at the
same advisory, so they are handled in a single PR:
| Alert | Package | Severity |
| --- | --- | --- |
| #119 | `go.opentelemetry.io/otel/sdk` | low |
| #120 | `go.opentelemetry.io/otel/exporters/otlp/otlptrace` | low |
| #121 | `go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc` |
low |
The advisory is *"Exporter config logging may leak endpoint URLs in info
logs"*: the OTLP exporters logged the resolved endpoint at info level, which
exposes any credentials embedded in the URL.
These modules are indirect dependencies here, pulled in through the
controller-runtime / Kubernetes client stack, so the change is confined to
`go.mod` and `go.sum`.
Side effects of `go mod tidy` after the bump:
- `github.com/go-logr/logr` `v1.4.3` -> `v1.4.4` and
`go.opentelemetry.io/proto/otlp` `v1.10.0` -> `v1.11.0`, required by otel
`v1.45.0`.
- `google.golang.org/genproto/googleapis/{api,rpc}` moved to the revision
otel `v1.45.0` depends on.
- `github.com/google/uuid` moved to the indirect block: it has no direct
import left in the tree, so `tidy` reclassifies it.
### Verification
- `go build ./...`
- `go vet ./...`
- `go test ./internal/... ./api/...`
### Checklist
- [x] I have explained the need for this PR and the problem it solves
- [x] I have explained the changes or the new features added to this PR
- [ ] I have added tests corresponding to this change
- [ ] I have updated the documentation to reflect this change
- [x] I have verified that this change is backward compatible (If not,
please discuss on the [APISIX mailing
list](https://github.com/apache/apisix/tree/master#community) first)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
