Many services allow you to create multiple api keys. Could we have something similar for uplink keys?
I’d like to create them at will, revoke them independently of each other, give them descriptive aliases and see some basic data on how they’re being used (e.g. most recent connection time).
Bonus points for including something in the server context that lets me see which key was being used.
I can certainly see uses for that, ahead, in my own App suite.
Right now, as a workaround, we need to create multiple Runtime Environments. Each can have its own Client and Server Uplink key.
But each also has other per-environment information (e.g., Database) that, in many cases, should be shared instead of duplicated. Undoing the duplication, with the current UI, is tedious and error-prone.
So other workarounds become necessary, e.g., a set of secondary keys, created, validated, and managed by the App itself, to be applied once the Anvil Uplink key succeeds. But I’d rather not reinvent Anvil’s wheels.