PipedreamHQ / PipedreamHQ/pipedream
[BUG] HTTP trigger custom token is still visible after save
Open
bug
tracked internally
triaged
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Describe the bug**
The HTTP trigger custom token is still visible after save, even though it says it won't be.
**To Reproduce**
Steps to reproduce the behavior:
1. Add an HTTP webhook
2. Configure Custom token auth
3. Save trigger
4. Go back to configuration and view custom token
**Expected behavior**
Not visible, just like secrets
**Screenshots**
Contributor guide
Assessment
This issue has not been assessed yet.