mirror of
https://github.com/supabase/supabase.git
synced 2026-09-07 02:20:52 +08:00
Creating publishable and secret keys adds them alongside the existing anon and service_role keys without affecting them. Make this explicit in two places so users don't assume their legacy keys are revoked: - Add an Admonition note to the API keys guide explaining both key types work simultaneously and legacy keys must be disabled in a separate step. - Update the "Create new API keys" dialog in Studio to reassure users that their existing anon and service_role keys remain valid.
88 lines
3.0 KiB
TypeScript
88 lines
3.0 KiB
TypeScript
import { useParams } from 'common'
|
|
import { useState } from 'react'
|
|
import { toast } from 'sonner'
|
|
import {
|
|
AlertDialog,
|
|
AlertDialogAction,
|
|
AlertDialogBody,
|
|
AlertDialogCancel,
|
|
AlertDialogContent,
|
|
AlertDialogDescription,
|
|
AlertDialogFooter,
|
|
AlertDialogHeader,
|
|
AlertDialogTitle,
|
|
Button,
|
|
} from 'ui'
|
|
import { Admonition } from 'ui-patterns/admonition'
|
|
|
|
import { useAPIKeyCreateMutation } from '@/data/api-keys/api-key-create-mutation'
|
|
|
|
export const CreateNewAPIKeysButton = () => {
|
|
const { ref: projectRef } = useParams()
|
|
|
|
const [createKeysDialogOpen, setCreateKeysDialogOpen] = useState(false)
|
|
const [error, setError] = useState<string | null>(null)
|
|
|
|
const { mutateAsync: createAPIKey } = useAPIKeyCreateMutation({ onError: () => {} })
|
|
|
|
const handleCreateNewApiKeys = async () => {
|
|
if (!projectRef) return
|
|
|
|
try {
|
|
setError(null)
|
|
|
|
// Create publishable key
|
|
try {
|
|
await createAPIKey({ projectRef, type: 'publishable', name: 'default' })
|
|
} catch (error: any) {
|
|
setError(`Failed to create the default publishable key: ${error.message}`)
|
|
throw error
|
|
}
|
|
|
|
// Create secret key
|
|
try {
|
|
await createAPIKey({ projectRef, type: 'secret', name: 'default' })
|
|
} catch (error: any) {
|
|
setError(
|
|
`The default publishable key was created, but the default secret key failed: ${error.message}`
|
|
)
|
|
throw error
|
|
}
|
|
|
|
setCreateKeysDialogOpen(false)
|
|
toast.success('Successfully created a new set of API keys!')
|
|
} catch (error) {
|
|
console.error('Failed to create API keys:', error)
|
|
throw error
|
|
}
|
|
}
|
|
|
|
return (
|
|
<AlertDialog open={createKeysDialogOpen} onOpenChange={setCreateKeysDialogOpen}>
|
|
<Button onClick={() => setCreateKeysDialogOpen(true)}>Create new API keys</Button>
|
|
<AlertDialogContent>
|
|
<AlertDialogHeader>
|
|
<AlertDialogTitle>Create new API keys</AlertDialogTitle>
|
|
<AlertDialogDescription>
|
|
This will create a default publishable key and a default secret key both named{' '}
|
|
<code className="break-keep! text-code-inline">default</code>. These keys are required
|
|
to connect your application to your Supabase project. Your existing legacy API keys (
|
|
<code className="break-keep! text-code-inline">anon</code> and{' '}
|
|
<code className="break-keep! text-code-inline">service_role</code>) are not affected and
|
|
remain valid until you disable them in a separate step.
|
|
</AlertDialogDescription>
|
|
</AlertDialogHeader>
|
|
{error && (
|
|
<AlertDialogBody>
|
|
<Admonition type="destructive" title="Unable to create API keys" description={error} />
|
|
</AlertDialogBody>
|
|
)}
|
|
<AlertDialogFooter>
|
|
<AlertDialogCancel>Cancel</AlertDialogCancel>
|
|
<AlertDialogAction onClick={handleCreateNewApiKeys}>Create keys</AlertDialogAction>
|
|
</AlertDialogFooter>
|
|
</AlertDialogContent>
|
|
</AlertDialog>
|
|
)
|
|
}
|