Running checkly login again on an already-authenticated machine creates an additional API key rather than rotating the existing one. Nothing warns that the previous key is still live, and the CLI gives no way to list or revoke keys, so they accumulate silently and can only be found in the web UI.
Request: either reuse the existing key, or revoke it on replacement, or at minimum print the fingerprint of the key being superseded and a pointer to where it can be revoked.
Please authenticate to join the conversation.
In Review
💡 Feature Request
1 day ago

Markus
Get notified by email when there are changes.
In Review
💡 Feature Request
1 day ago

Markus
Get notified by email when there are changes.