tests/e2e: bump retries

Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>

authentik/lib/models.py

@@ -1,7 +1,6 @@
 """Generic models"""
 import re
 
-from django.core.exceptions import ValidationError
 from django.core.validators import URLValidator
 from django.db import models
 from django.utils.regex_helper import _lazy_re_compile

tests/e2e/utils.py

@@ -30,7 +30,7 @@ from authentik.core.models import User
 from authentik.core.tests.utils import create_test_admin_user
 from authentik.managed.manager import ObjectManager
 
-RETRIES = int(environ.get("RETRIES", "3"))
+RETRIES = int(environ.get("RETRIES", "5"))
 
 
 def get_docker_tag() -> str:

website/docs/terminology.md

@@ -25,18 +25,22 @@ A Provider is a way for other applications to authenticate against authentik. Co
 
 At a base level a policy is a yes/no gate. It will either evaluate to True or False depending on the Policy Kind and settings. For example, a "Group Membership Policy" evaluates to True if the user is member of the specified Group and False if not. This can be used to conditionally apply Stages, grant/deny access to various objects, and for other custom logic.
 
-### Stages
+See [Policies](./policies/index.md)
+
+### Stages & Stages
+
+Flows are an ordered sequence of stages. These flows can be used to define how a user authenticates, enrolls, etc.
 
 A stage represents a single verification or logic step. They are used to authenticate users, enroll users, and more. These stages can optionally be applied to a flow via policies.
 
-### Flows
-
-Flows are an ordered sequence of stages. These flows can be used to define how a user authenticates, enrolls, etc.
+See [Flows](./flow/flows.md)
 
 ### Property Mappings
 
 Property Mappings allow you to make information available for external applications. For example, if you want to login to AWS with authentik, you'd use Property Mappings to set the user's roles in AWS based on their group memberships in authentik.
 
+See [Property Mappings](./property-mappings/index.md)
+
 ### Outpost
 
 An outpost is a separate component of authentik, which can be deployed anywhere, regardless of the authentik deployment. The outpost offers services that aren't implemented directly into the authentik core, like Reverse Proxying.