providers/scim: optimize sending all members within a group

[BeryJu]

Details

Whenever possible, send group members as a patch after creating/updating a group. This makes it basically the last resort to send all groups in a big chunk since that can be quite resource intensive for SCIM remotes

---

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	1e39705
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-storybook/deploys/66c73e047ffba500085b6a0c

[netlify]

✅ Deploy Preview for authentik-docs canceled.

Name	Link
🔨 Latest commit	1e39705
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-docs/deploys/66c73e044360dd00083b0682

[codecov]

Codecov Report

Attention: Patch coverage is 86.20690% with 4 lines in your changes missing coverage. Please review.

Project coverage is 92.69%. Comparing base (e428e4c) to head (1e39705).
Report is 2 commits behind head on main.

Files	Patch %	Lines
authentik/providers/scim/clients/groups.py	82.60%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9968      +/-   ##
==========================================
- Coverage   92.76%   92.69%   -0.08%     
==========================================
  Files         736      736              
  Lines       36360    36377      +17     
==========================================
- Hits        33730    33719      -11     
- Misses       2630     2658      +28     

Flag	Coverage Δ
e2e	49.16% <20.68%> (-0.12%)	⬇️
integration	25.04% <0.00%> (-0.02%)	⬇️
unit	90.24% <86.20%> (+<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.

[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-f0cbe59ddb030a025e1fa14a8b385bc87c674e6a
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-f0cbe59ddb030a025e1fa14a8b385bc87c674e6a-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-f0cbe59ddb030a025e1fa14a8b385bc87c674e6a

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-f0cbe59ddb030a025e1fa14a8b385bc87c674e6a-arm64

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