Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(frontend)[Vault Hot Fix]: Stale secret state causing 404 when adding secrets after deletion #2395

Conversation

bekossy
Copy link
Member

@bekossy bekossy commented Dec 27, 2024

Description

When you delete a secret, and try to create/add a new one, the request fails with a 404. But when you reload the page, and try to create/add a new one, it works. I think that in the first instance, the state saves the deleted secret id which results to a 404.

@bekossy bekossy requested a review from ardaerzin December 27, 2024 09:14
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Dec 27, 2024
Copy link

vercel bot commented Dec 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
agenta ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 27, 2024 9:14am
agenta-documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 27, 2024 9:14am

@dosubot dosubot bot added the bug Something isn't working label Dec 27, 2024
@aybruhm aybruhm merged commit 372c4e7 into dev Dec 27, 2024
5 of 6 checks passed
@aybruhm aybruhm deleted the hot-fix/-stale-secret-state-causing-404-when-adding-secrets-after-deletion branch December 27, 2024 09:58
aybruhm added a commit that referenced this pull request Feb 13, 2025
…ausing-404-when-adding-secrets-after-deletion

(frontend)[Vault Hot Fix]: Stale secret state causing 404 when adding secrets after deletion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants