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.
527 B
527 B
title
| title |
|---|
| Managing flow context keys |
Flow context can be managed in Expression policies via the context['flow_plan'].context variable.
Here's an example of setting a key in an Expression policy:
context['flow_plan'].context['redirect_stage_target'] = 'ak-flow://redirected-authentication-flow'
And here's an example of removing that key:
context['flow_plan'].context.pop('redirect_stage_target', None)