You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
I encountered an issue with Devvit Setting / Secret Storage. When I was developing app I added a secret to my devvit app.
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.
But with this change when I grab the key using the
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.
The text was updated successfully, but these errors were encountered: