core: fix migrations missing using db_alias

[rissson]

Details

Closes #9866

---

Checklist

• Local tests pass (ak test authentik/)
• The code has been formatted (make lint-fix)

If an API change has been made

• The API schema has been updated (make gen-build)

If changes to the frontend have been made

• The code has been formatted (make web)

If applicable

• The documentation has been updated
• The documentation has been formatted (make website)

[netlify]

✅ Deploy Preview for authentik-storybook canceled.

Name	Link
🔨 Latest commit	dba17ee
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-storybook/deploys/668c1c93aaaa7d00081a083b

[netlify]

✅ Deploy Preview for authentik-docs canceled.

Name	Link
🔨 Latest commit	dba17ee
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-docs/deploys/668c1c932b37280008460468

[BeryJu]

Should probably make the same change in 0029_provider_backchannel_applications_and_more.py

[rissson]

Should probably make the same change in 0029_provider_backchannel_applications_and_more.py

Yeah I'm reading all RunPython migrations to make sure we're .using(db_alias) everywhere

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.62%. Comparing base (5c8a9ab) to head (dba17ee).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10409      +/-   ##
==========================================
+ Coverage   92.61%   92.62%   +0.01%     
==========================================
  Files         714      714              
  Lines       35012    35012              
==========================================
+ Hits        32425    32430       +5     
+ Misses       2587     2582       -5     

Flag	Coverage Δ
e2e	49.60% <ø> (+0.01%)	⬆️
integration	25.37% <ø> (ø)
unit	90.12% <ø> (-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.

[rissson]

Further question, how a manytomany reverse relations handled? For instance should we use flow.policies.set([]) or flow.policies.using(db_alias).set([])?

[rissson]

Also, there is an event migration that uses authentik.events.utils.get_user, which we might need to change to allow passing a db_alias in there.

This is actually fine.

[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-ghcr.io/goauthentik/dev-server:gh-dba17ee6deaa15cd0b7d31ffa89ce86301277bec
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s

For arm64, use these values:

AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-ghcr.io/goauthentik/dev-server:gh-dba17ee6deaa15cd0b7d31ffa89ce86301277bec-arm64
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
image:
    repository: ghcr.io/goauthentik/dev-server
    tag: gh-ghcr.io/goauthentik/dev-server:gh-dba17ee6deaa15cd0b7d31ffa89ce86301277bec

For arm64, use these values:

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

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

[BeryJu]

/cherry-pick version-2024.6