redpanda-data / redpanda-data/benthos
Deprecated golang.org/x/oauth2 error with latest Benthos version
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 571
- Forks
- 120
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 18
Description
Hey, I'm currently upgrading our Benthos, and I see this error in logs
deprecated: golang.org/x/oauth2: Transport.CancelRequest no longer does anything; use context
We're using oAuth2 auth with our pipelines.
processor_resources:
- label: analyze_http
http:
parallel: true
drop_on: [500, 501, 400, 404, 403, 406]
backoff_on: [408, 429, 502, 503, 504]
max_retry_backoff: "120s"
timeout: "60s"
url: "x"
verb: POST
headers:
Content-Type: application/json
Content-Encoding: gzip
oauth2:
enabled: true
client_key: xxxxxx # Consumer app clientId
client_secret: xxxxxx # consumer app secret
token_url: xxxxxx
scopes:
- xxxxxx # API app clientId
rate_limit: 100
Do you know if I should be worries about it? Should we modify a setting?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warning with the shown HTTP processor configuration and OAuth2 settings. Trace the HTTP processor's OAuth2 entry point to determine whether the deprecated Transport.CancelRequest call affects pipeline behavior; done means confirming the impact and identifying the required configuration or dependency change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100