tasks: delay startup signals

[rissson]

There somehow is a race condition when starting up the worker, that makes some tasks inexistent even though they actually have been inserted. Here we simply delay the start of the consumers so we can completely finish the startup and only then grab tasks and process them.

Closes #17749

[BeryJu]

I dont like this solution....but I dont have a better idea either

[netlify]

✅ Deploy Preview for authentik-docs canceled.

Name	Link
🔨 Latest commit	e08a84b
🔍 Latest deploy log	https://app.netlify.com/projects/authentik-docs/deploys/6900fc8e2f19050008cf8402

[netlify]

✅ Deploy Preview for authentik-storybook canceled.

Name	Link
🔨 Latest commit	e08a84b
🔍 Latest deploy log	https://app.netlify.com/projects/authentik-storybook/deploys/6900fc8d112c94000847f38b

[netlify]

✅ Deploy Preview for authentik-integrations canceled.

Name	Link
🔨 Latest commit	e08a84b
🔍 Latest deploy log	https://app.netlify.com/projects/authentik-integrations/deploys/6900fc8eebaf420008e46f68

[rissson]

I dont like this solution....but I dont have a better idea either

maybe a ctxvar that gets set to true after one of the startup signals have been sent?

[codecov]

Codecov Report

❌ Patch coverage is 42.85714% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 92.98%. Comparing base (9b6aa56) to head (e08a84b).
⚠️ Report is 82 commits behind head on main.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
authentik/tasks/middleware.py	42.85%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17769      +/-   ##
==========================================
+ Coverage   92.88%   92.98%   +0.10%     
==========================================
  Files         869      869              
  Lines       47950    47952       +2     
==========================================
+ Hits        44538    44589      +51     
+ Misses       3412     3363      -49     

Flag	Coverage Δ
e2e	45.27% <42.85%> (+0.44%)	⬆️
integration	23.19% <42.85%> (+<0.01%)	⬆️
unit	91.07% <42.85%> (+0.01%)	⬆️
unit-migrate	91.12% <42.85%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cheggerdev]

I dont like this solution....but I dont have a better idea either

maybe a ctxvar that gets set to true after one of the startup signals have been sent?

This is called a semaphore. 😄

[rissson]

looking at the tests, yeah, this is not working

[rissson]

that's better

[authentik-automation]

🍒 Cherry-pick to version-2025.10 created: #17775

[github-actions]

authentik PR Installation instructions

Instructions for docker-compose

Add the following block to your .env file:

AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-e08a84bc73e8a03fa62fe300a959fc8f3d556884
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s

Afterwards, run the upgrade commands from the latest release notes.

Instructions for Kubernetes

Add the following block to your values.yml file:

authentik:
    outposts:
        container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
global:
    image:
        repository: ghcr.io/goauthentik/dev-server
        tag: gh-e08a84bc73e8a03fa62fe300a959fc8f3d556884

Afterwards, run the upgrade commands from the latest release notes.

[authentik-automation]

⚠️ Cherry-pick to version-2025.8 has conflicts: #18008