website/docs: add links and tweaks to existing docs on flow executors#10340
website/docs: add links and tweaks to existing docs on flow executors#10340
Conversation
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for authentik-storybook canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10340 +/- ##
=======================================
Coverage 92.64% 92.65%
=======================================
Files 713 713
Lines 34978 34978
=======================================
+ Hits 32407 32409 +2
+ Misses 2571 2569 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
kensternberg-authentik
left a comment
There was a problem hiding this comment.
Generally fine. A few suggestions, nothing major.
| title: Flow executor (backend) | ||
| --- | ||
|
|
||
| A big focus of authentik is the flows system, which allows you to combine and build complex conditional processes using stages and policies. Normally, these flows are executed in the browser using the authentik inbuilt flow executor (/if/flows). |
There was a problem hiding this comment.
You know, I don't think we need to use "inbuilt" or "default." Something that suggests what it's for rather than its position in a hierarchy of executors. "...using authentik's standard browser-based flow executor..." maybe? That way the rest of the conversation can be about non-standard (SFE) or non-browser (headless) executors.
| A big focus of authentik is the flows system, which allows you to combine and build complex conditional processes using stages and policies. Normally, these flows are automatically executed in the browser using authentik's frontend [default flow executor (/if/flows)](../../docs/flow/executors/if-flow.md). | ||
|
|
||
| However, any flow can be executed via an API from anywhere, in fact that is what the Web flow executor does. This means, you can, with a few requests, execute flows from anywhere, and integrate authentik even better. | ||
| However, any flow can be executed via an API from anywhere, in fact that is what the backend flow executor does. This means, you can, with a few requests, execute flows from anywhere, and integrate authentik even better. |
There was a problem hiding this comment.
Suggestion: "With a few requests you can execute flows from any device and integrate authentik more fully into your workflows."
Otherwise it reads, a bit, like, William Shatner!, when he's, monologuing!
|
authentik PR Installation instructions Instructions for docker-composeAdd the following block to your AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-ghcr.io/goauthentik/dev-server:gh-b055bf4f033f34eac5922e8a6f7ef8a61270dea8
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)sFor arm64, use these values: AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-ghcr.io/goauthentik/dev-server:gh-b055bf4f033f34eac5922e8a6f7ef8a61270dea8-arm64
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)sAfterwards, run the upgrade commands from the latest release notes. Instructions for KubernetesAdd the following block to your 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-b055bf4f033f34eac5922e8a6f7ef8a61270dea8For 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-b055bf4f033f34eac5922e8a6f7ef8a61270dea8-arm64Afterwards, run the upgrade commands from the latest release notes. |
* main: website/docs: add links and tweaks to existing docs on flow executors (#10340) sources/saml: fix pickle error, add saml auth tests (#10348) web: bump API Client version (#10351) core: applications api: add option to only list apps with launch url (#10336) website/integrations: minio: configure openid on web (#9874) website/docs: integrations: gitea: specify callback url (#10180) providers/saml: fix metadata import error handling (#10349) core, web: update translations (#10341) core: bump twilio from 9.2.2 to 9.2.3 (#10343) core: bump google-api-python-client from 2.135.0 to 2.136.0 (#10344) translate: Updates for file web/xliff/en.xlf in zh-Hans (#10339) translate: Updates for file web/xliff/en.xlf in zh_CN (#10338) web: bump the storybook group in /web with 7 updates (#10263) web: lintpicking (#10212)
* main: website/docs: add links and tweaks to existing docs on flow executors (#10340) sources/saml: fix pickle error, add saml auth tests (#10348) web: bump API Client version (#10351) core: applications api: add option to only list apps with launch url (#10336) website/integrations: minio: configure openid on web (#9874) website/docs: integrations: gitea: specify callback url (#10180) providers/saml: fix metadata import error handling (#10349) core, web: update translations (#10341) core: bump twilio from 9.2.2 to 9.2.3 (#10343) core: bump google-api-python-client from 2.135.0 to 2.136.0 (#10344) translate: Updates for file web/xliff/en.xlf in zh-Hans (#10339) translate: Updates for file web/xliff/en.xlf in zh_CN (#10338) web: bump the storybook group in /web with 7 updates (#10263) web: lintpicking (#10212)
These changes add links between the backend Flow Exececutor and the frontend, defaul flow executor. Also a link to the Brands docs, and a few edits and clairifcations.
I did not add info about the upcoming SFE executor.
make website)