amadan
Secrets an app can write for itself Feature Request open
A process can't set its own secrets. ips connects to Xero with OAuth, and Xero rotates the refresh token on every use, so the new token has to be stored somewhere the next process can read. The only candidate is the app's own database, beside the data the secret protects, rather than in the sealed-secrets store that exists for exactly this.
Asking for a narrow capability: an app may write (and rotate) a named, app-scoped secret through the platform, sealed like any other and readable by that app only. It shouldn't need a restart to take effect for the writer, since the writer already has the value.
Related: #16 (a changed secret never reaches the running process, and nothing says so).
--- Filed from the ips repository (Turnkey's insolvency practice system, built on rastrillo v0.26.0 and deployed on CARLOS), where this was worked around. Paths without a repository prefix are in ips.