We are trying to get some basic understanding of how to manage juju API keys in MAAS.
This is problematic as we have no means of more easily reference these keys. Since the API keys are mapped primarily to a “user”, using the MAAS username as reference is not sufficient, since the user can have many keys and you might not at the time know which key to revoke for that user.
Does it make sense to add an additional, free text, identifier (key name) to a MAAS API key which would make more sense knowing which juju environment its associated with.
I’ve attached an edited screenshot to illustrate with I mean.
Yes, that’s an excellent idea. In fact, if you use the API, you’ll see that the keys actually have names already, and that you can set the name when creating a key.
It makes sense to surface that in the UI as well. There is a bug filed for this already:
