Masking secrets in the config for benthos streams
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
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.
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
- Dominant language
- Go
- Stars
- 578
- Forks
- 124
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from redpanda-data/benthos
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
redpanda-data/benthos#404 ·
Maintainers usually reply within 3 days
-
Streams mode: spans carry no stream identityPossibly taken @alexander-zimmermann claimed this 47 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
redpanda-data/benthos#503 ·
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
redpanda-data/benthos#502 ·
Maintainers usually reply within 3 days
-
streams API: support per-request `env` overrides for config templatingPossibly taken @g-hurst claimed this 68 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 72/100
redpanda-data/benthos#481 ·
Maintainers usually reply within 3 days
-
http_server input can get permanently stuck returning 503 after a stream restart (stream mode)Possibly taken @masnnuller claimed this 84 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
redpanda-data/benthos#469 ·
Maintainers usually reply within 3 days
All issues in redpanda-data/benthos
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
agent-butler-finding bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jordansmall/spindrift#6161 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-telemetry/opentelemetry-go-compile-instrumentation#1635 ·
Maintainers usually reply within 2 days
-
C-bug O-community X-blathers-untriaged
Difficulty 1/5 Under an hour Newbie friendliness 84/100
cockroachdb/cockroach#176210 · 1 comment ·
-
VLAgent `spec.k8sCollector.includePodLabels: false` has no effectPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
VictoriaMetrics/operator#2772 ·
Maintainers usually reply within 1 day