Devvit Secret shadows Devvit Setting even after being deleted.
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- typescript
- Área
- developer-experience
Línea de trabajo
Start by reproducing the issue with the two Devvit.addSettings definitions and the ctx.settings.get("Gemini-API-Key") call, changing the setting from an app-scoped secret to an installation-scoped setting. Trace how settings and secret storage are resolved; done means the installation value is returned after the secret is removed, or a documented CLI deletion path is provided.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I encountered an issue with Devvit Setting / Secret Storage. When I was developing app I added a secret to my devvit app.
Devvit.addSettings([
{
name: "Gemini-API-Key",
label: "Gemini API Key",
type: "string",
scope: "app",
helpText: "Enter your Gemini API Key here",
isSecret: true
},
]);
Later I ended up changing my mind and made it per install app because I thought it would be better if ever user brought their own api instead of using mine.
Devvit.addSettings([
{
name: "Gemini-API-Key",
label: "Gemini API Key",
type: "string",
scope: "installation",
helpText: "Enter your Gemini API Key here",
},
]);
But with this change when I grab the key using the
const apiKey = (await ctx.settings.get("Gemini-API-Key")) as string;
It still grabs the old secret that I set instead of the new value from app setting page. So even when I stopped using the secret, the secret still somehow exist in the Devvit system.
Devvit needs to automatically clear secrets if they are not being referred in the code and free up its namespace. Or at least provide a cmd in devvit cli to delete all secret storage for an app.
- Lenguaje dominante
- TypeScript
- Estrellas
- 210
- Forks
- 88
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de reddit/devvit
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 42/100
Todos los issues de reddit/devvit
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
[Bug]: Matrix progress drafts fail with "Matrix runtime not initialized" during tool activity Abiertobug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Client support matrix inclusion Abiertoenhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
calcite-components needs triage refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Esri/calcite-design-system#15203 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
danielmiessler/LifeOS#2218 ·