corebot
corebot copied to clipboard
Dynamic rundeck API key
Currently, you set the rundeck API key at startup. This means if you need to reset the API key, you need to restart the daemon.
Being able to set the key via chat, and have it associated with an account means we can improve security in the back half (rundeck) by issuing keys that expire, and control how the key is issued (ie, MFA type security.)
I'd suggest that this only works on accounts that have an ACL associated with them.
Hi @ThomasADavis, thanks for raising. I’d be happy to support this feature. Do you think you might be in a position to contribute a PR for this?