From 693cf0486dd261df5076f6e6f9b6deb830595caf Mon Sep 17 00:00:00 2001 From: Andras Bacsai <5845193+andrasbacsai@users.noreply.github.com> Date: Fri, 6 Nov 2026 11:22:49 +0100 Subject: [PATCH] fix(ui): link secret manager token forms to their provider dashboards Co-Authored-By: Claude Opus 5.5 --- .../security/integration-token-form.blade.php | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/resources/views/livewire/security/integration-token-form.blade.php b/resources/views/livewire/security/integration-token-form.blade.php index 4f029f6318..642d176a80 100644 --- a/resources/views/livewire/security/integration-token-form.blade.php +++ b/resources/views/livewire/security/integration-token-form.blade.php @@ -105,18 +105,30 @@
Recommended Doppler token

Use a read-only Service Token (dp.st.*). It is pinned to one project and config. Create it in Doppler under Project > Config > Access.

+ + Open Doppler dashboard + + @elseif ($provider === 'infisical')
Infisical machine identity

Create a machine identity with Universal Auth and read access to your project. Paste the client ID above and the client secret in the secret field.

+ + Open Infisical Cloud + +
@elseif ($provider === 'vault')
Vault token

Use a token with read access to your KV v2 secrets. Prefer a periodic or long-lived token — deployments fail when the token expires.

+ + Open HCP Vault + +
@endif