github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #1357] OpenID Connect Force Availability #6368

New Issue
Closed
opened 2026-04-20 16:57:39 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 16:57:39 -05:00
Owner
Copy Link

Originally created by @xeruf on GitHub (Aug 30, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1357

Originally assigned to: @Copilot on GitHub.

Description

We regularly have the issue that we find ourselves with an unusable instance of Vikunja on our Kubernetes cluster because somehow the OpenID Connect provider check of Vikunja fails as it starts.

A flag to force the providers availability, crashing vikunja if it is unable to connect at startup, would be very handy - this allows kubernetes to handle missing dependencies automatically.

See https://community.vikunja.io/t/openid-connect-force-availability/3499/2

Vikunja Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @xeruf on GitHub (Aug 30, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1357 Originally assigned to: @Copilot on GitHub. ### Description We regularly have the issue that we find ourselves with an unusable instance of Vikunja on our Kubernetes cluster because somehow the OpenID Connect provider check of Vikunja fails as it starts. A flag to `force` the providers availability, crashing vikunja if it is unable to connect at startup, would be very handy - this allows kubernetes to handle missing dependencies automatically. See https://community.vikunja.io/t/openid-connect-force-availability/3499/2 ### Vikunja Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:57:41 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 31, 2025):

Now implemented in https://github.com/go-vikunja/vikunja/pull/1358

<!-- gh-comment-id:3239851876 --> @kolaente commented on GitHub (Aug 31, 2025): Now implemented in https://github.com/go-vikunja/vikunja/pull/1358
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6368
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?