pipedv1: Mask the plugins config in a piped config
Open
Nobody has claimed this yet.
area/pipedv1
kind/enhancement
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What would you like to be added:
Mask some fields in plugins in a piped config.
We need a discussion on how to realize this feature.
Why is this needed:
In pipedv0, some fields in the piped config were masked to hide secret values on the Web UI.
However, in pipedv1, piped core does not know which fields should be masked.
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 reading the piped config fields in pkg/configv1/piped.go at the linked lines, then compare them with the pipedv0 masking behavior described in the issue. The work is complete when the masking approach, fields to protect, and implementation scope are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100