Redundant KV Keys

i'm noticing several redundant keys being made when using secondary storage (attached) here's my secondaryStorage from auth.ts
// ...

secondaryStorage: {
get: async (key) => {
return await upstash.get(key)
},
set: async (key, value, ttl) => {
if (ttl) await upstash.set(key, value, { ex: ttl })
else await upstash.set(key, value)
},
delete: async (key) => {
await upstash.del(key)
},
},

// ...
// ...

secondaryStorage: {
get: async (key) => {
return await upstash.get(key)
},
set: async (key, value, ttl) => {
if (ttl) await upstash.set(key, value, { ex: ttl })
else await upstash.set(key, value)
},
delete: async (key) => {
await upstash.del(key)
},
},

// ...
i'm curious as to why these keys exist.
No description
No description
2 Replies
begot
begotOP3w ago
likely related https://github.com/better-auth/better-auth/pull/4502 would be nice to be able to only store auth routes
begot
begotOP3w ago
@admin any info on this?

Did you find this page helpful?