redpanda-data / redpanda-data/benthos
Masking secrets in the config for benthos streams
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 571
- Forks
- 120
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 18
Description
I am trying to generate a config via a microservice and POST it to benthos streams. I need to get back response constructed as part of config to my service hence I am using http_server input and sync_response output. The issue is since the POST call is http, managing secrets becomes challenging. The way I could think of now is to have a https call.
Is it possible to configure this for benthos streams I mean enabling TLS using key and cert file fields of http_server input? How would the post call differ in that case?
I am also open to any other suggestions other than the above approach.
Note: I can have multiple streams running and multiple secrets to manage for that respective streams
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 with the http_server input and sync_response output configuration, and trace how POST requests are handled. Determine whether TLS can use key and cert file fields and document how clients should change their POST calls. Also clarify a secure approach for multiple streams and per-stream secrets; done means a concrete supported configuration or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100