You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8491915
Browse filesBrowse the repository at this point in the historyBrowse files
feat(webapp): show hidden root API keys masked and allow regenerating them
The API keys page now always lists the root API key. A hidden root key
shows masked to its last 4 characters and can be regenerated, but never
revealed or copied. When it's hidden and you have no other keys, the
page prompts you to create an API key for your backend.
"Revoke the previous key immediately" now also stops older root keys
still in their 24-hour grace window.
Mono-RevId: e0466df43d3fae68e32f01da137835ea3dec4858
The API keys page now always lists your root API key, masked to its last 4 characters when it's hidden, so you can regenerate it and revoke the previous key. When the root key is hidden, the page points you to creating an API key for your backend.
label="Keep the previous key working for 24 hours"
94
-
description="Roll out the new key to your environment variables without downtime. The previous key stops working after 24 hours."
99
+
description={
100
+
isRootApiKeyHidden
101
+
? "Anything still using the previous key keeps working for 24 hours."
102
+
: "Roll out the new key to your environment variables without downtime. The previous key stops working after 24 hours."
103
+
}
95
104
/>
96
105
<RadioGroupItem
97
106
id="previousKey-revoke"
98
107
value="revoke"
99
108
variant="description"
100
109
label="Revoke the previous key immediately"
101
-
description="Choose this if the key may have leaked. Deployments and services still using the previous key will fail until they are updated with the new key."
110
+
description={
111
+
isRootApiKeyHidden
112
+
? "Choose this if the key may have leaked. It stops working now, along with any older key still in its 24-hour window."
113
+
: "Choose this if the key may have leaked. It stops working now, along with any older key still in its 24-hour window. Deployments and services still using them will fail until they are updated with the new key."
0 commit comments