Commit 626d845
committed
fix(secrets): let server visibility outrank the carried rename
The carried value won over the server map, so a rename-back (or a
rename onto an existing key) left an entry shadowing a key that still
has a credential: a later confirmed convert-to-secret would apply
server-side while the row stayed under Workspace variables and kept
rendering unmasked until refresh.
Server state now wins wherever it exists and the carried value only
fills the gap where it doesn't, which is all it was ever for. A stale
entry is inert under that ordering rather than needing to be cleared on
every path that could invalidate it.1 parent 2e771db commit 626d845
1 file changed
Lines changed: 11 additions & 5 deletions
File tree
- apps/sim/app/workspace/[workspaceId]/settings/components/secrets/components/secrets-manager
Lines changed: 11 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
904 | 904 | | |
905 | 905 | | |
906 | 906 | | |
907 | | - | |
908 | | - | |
909 | | - | |
910 | | - | |
911 | | - | |
| 907 | + | |
| 908 | + | |
| 909 | + | |
| 910 | + | |
| 911 | + | |
| 912 | + | |
| 913 | + | |
| 914 | + | |
| 915 | + | |
| 916 | + | |
| 917 | + | |
912 | 918 | | |
913 | 919 | | |
914 | 920 | | |
| |||
0 commit comments