mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #3879] [bug]: Secrets variable not persistent #1365
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1365
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Leon-Luu on GitHub (Mar 7, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3879
Is there an existing issue for this?
Current behavior
When created a Secret variables and saved. After logout and login from the Hoppscotch the secrets are lost. Show secret is not showing any values anymore.
This is easy to reproduce with incognito modes or changing browsers.
The same issue happens on the secrets within the local workspaces and the Team environment secrets.
After login secrets values disappeared:

Steps to reproduce
Environment
Production
Version
Cloud
@thetronjohnson commented on GitHub (Mar 8, 2024):
Hi @Leon-Luu, This is the expected behavior for secret variables. Because secrets variables can be used to store sensitive information such as passwords or other credentials, the secret variable values are never synced with Hoppscotch.
https://docs.hoppscotch.io/documentation/features/environments#types-of-variables-in-an-environment
@Leon-Luu commented on GitHub (Mar 8, 2024):
Hi Kiran, yes seems to be expected with populating the values of the variable at runtime and not sync. I'll close this issue.