Files
authentik/docs/topics/customize/blueprints/v1/meta.md
Teffen Ellis 582812b3ec website: Flesh out docs split.
website: Copy files during build.

website: Allow for mixed env builds.

website: Reduce build size.

website: Expose build.

website: Add build memory debugging.

WIP: Disable broken links check to compare memory usage.

website: Update deps.

website: Clean up API paths.

website: Flesh out 3.8 fixes.

Format.

website: Update ignore paths.

Website: Clean up integrations build.

website: Fix paths.

website: Optimize remark.

website: Update deps.

website: Format.

website: Remove linking.

website: Fix paths.

wip: Attempt API only build.

Prep.

Migrate render to runtime. Tidy sidebar.

Clean up templates.

docs: Move directory. WIP

docs: Flesh out split.

website: Fix issue where routes have collisions.
2025-07-01 21:53:19 +02:00

1.1 KiB

Meta models

Since blueprints have a pretty strict mapping of each entry mapping to an instance of a model in the database, meta models exist to trigger other actions within authentik that don't directly map to a model.

authentik_blueprints.metaapplyblueprint

This meta model can be used to apply another blueprint instance within a blueprint instance. This allows for dependency management and ensuring related objects are created.

See examples in the default blueprints for more information.

Attributes

  • identifiers: Key-value attributes used to match the blueprint instance

    Example:

    attrs:
        identifiers:
            name: Default - Password change flow
    
  • required: (Default: true) Configure if the blueprint instance must exist

    If this is set to true and no blueprint instance matches the query above, an error will be thrown. Otherwise, execution will continue without applying anything extra.