mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 17:35:10 +03:00
How to test: 1. Connect a project to GH repo 2. Deploy the `config.toml` once 3. Change some setting in Auth 4. You should see a change in `/dashboard/project/_/settings/code-configuration` <img width="1271" height="1186" alt="Screenshot 2026-09-16 at 16 26 39" src="https://github.com/user-attachments/assets/dfc135a4-e495-489e-88fd-b760383793b4" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Configuration drift comparisons now use a consistent project configuration schema. - Drift details display complete current-environment and `config.toml` values, grouped by section. - Matching and unmanaged settings are organized into dedicated sections. - Configuration fields link directly to relevant Studio settings. - Added a warning that GitHub deployments overwrite local changes. - **Bug Fixes** - Configuration updates now refresh project configuration data automatically. - Improved labels and formatting for boolean and redirect URL values. - Drift errors identify invalid configuration paths and provide corrective guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
69 lines
2.3 KiB
TypeScript
69 lines
2.3 KiB
TypeScript
import { useMutation, useQueryClient } from '@tanstack/react-query'
|
|
import { toast } from 'sonner'
|
|
|
|
import { sslEnforcementKeys } from './keys'
|
|
import { configKeys } from '@/data/config/keys'
|
|
import { handleError, put } from '@/data/fetchers'
|
|
import { jitDbAccessKeys } from '@/data/jit-db-access/keys'
|
|
import type { ResponseError, UseCustomMutationOptions } from '@/types'
|
|
|
|
export type SSLEnforcementUpdateVariables = {
|
|
projectRef: string
|
|
requestedConfig: { database: boolean }
|
|
}
|
|
|
|
export type SSLEnforcementUpdateResponse = {
|
|
appliedSuccessfully: boolean
|
|
currentConfig: { database: boolean }
|
|
error?: any
|
|
}
|
|
|
|
export async function updateSSLEnforcement({
|
|
projectRef,
|
|
requestedConfig,
|
|
}: SSLEnforcementUpdateVariables) {
|
|
if (!projectRef) throw new Error('projectRef is required')
|
|
|
|
const { data, error } = await put(`/v1/projects/{ref}/ssl-enforcement`, {
|
|
params: { path: { ref: projectRef } },
|
|
body: { requestedConfig },
|
|
})
|
|
|
|
if (error) handleError(error)
|
|
return data
|
|
}
|
|
|
|
type SSLEnforcementUpdateData = Awaited<ReturnType<typeof updateSSLEnforcement>>
|
|
|
|
export const useSSLEnforcementUpdateMutation = ({
|
|
onSuccess,
|
|
onError,
|
|
...options
|
|
}: Omit<
|
|
UseCustomMutationOptions<SSLEnforcementUpdateData, ResponseError, SSLEnforcementUpdateVariables>,
|
|
'mutationFn'
|
|
> = {}) => {
|
|
const queryClient = useQueryClient()
|
|
|
|
return useMutation<SSLEnforcementUpdateData, ResponseError, SSLEnforcementUpdateVariables>({
|
|
mutationFn: (vars) => updateSSLEnforcement(vars),
|
|
async onSuccess(data, variables, context) {
|
|
const { projectRef } = variables
|
|
await queryClient.invalidateQueries({ queryKey: sslEnforcementKeys.list(projectRef) })
|
|
// JIT DB access can report `unavailableReason: 'ssl_enforcement_required'`,
|
|
// so its status needs to be refetched whenever SSL enforcement changes.
|
|
await queryClient.invalidateQueries({ queryKey: jitDbAccessKeys.list(projectRef) })
|
|
await queryClient.invalidateQueries({ queryKey: configKeys.projectConfig(projectRef) })
|
|
await onSuccess?.(data, variables, context)
|
|
},
|
|
async onError(data, variables, context) {
|
|
if (onError === undefined) {
|
|
toast.error(`Failed to update SSL enforcement: ${data.message}`)
|
|
} else {
|
|
onError(data, variables, context)
|
|
}
|
|
},
|
|
...options,
|
|
})
|
|
}
|