Upgrading directly the newest recipe version breaks Authentik #25
Reference in New Issue
Block a user
No description provided.
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?
I attempted to deploy the lastest version of the Authentik recipe from
cfb8c021, and encountered the same issue outlined in https://github.com/goauthentik/authentik/issues/20634Apparently, it is not possible to update authentik directly to the newest version: it must be upgraded to each intermediate version in sequence, as outlined at https://docs.goauthentik.io/install-config/upgrade/
Is it possible to guard against this pattern by detecting and prevent unsafe deployments like this, or otherwise display a warning? This seems like a very easy mistake to make.