Twitter 1 BE | injecting App key + secret when launching docker container in k8s (2)
Twitter has an app key and app secret that have to stay secret to the user
Implementation Store as k8s secret (?) Container accepts arguments for TWITTER_APP_KEY and TWITTER_APP_SECRET TODO Plugin looks if env variables exist, else uses keys from metadata.json or separate auth.json (for local running)
only open question: how to inject keys from flutter app with local pod
Options add as CI secret in Twitter plugin, only insert in kubernetes container (see Pod ci) best choice, no hacking Plugin needs to read environment variables if they exist, else read from metadata.jsonneed to insert it when launching container but currently now way to differentiate between which plugin (only twitter should get it) possible: only pass variables when plugin == twitter alternative: k, v pair store in hosting where the plugin can pull from when already running but all plugins will have access, someone can just build plugin to read all secrets required: if plugin = twitter: .... Possible: new AuthService backend that handles credentials seems long-term solution