Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blueprints: allow setting of token key in blueprint context #4995

Merged
merged 1 commit into from Mar 17, 2023

Conversation

BeryJu
Copy link
Member

@BeryJu BeryJu commented Mar 17, 2023

closes #4717

closes #4717

Signed-off-by: Jens Langhammer <jens@goauthentik.io>
@netlify
Copy link

netlify bot commented Mar 17, 2023

Deploy Preview for authentik ready!

Name Link
🔨 Latest commit 7f84d49
🔍 Latest deploy log https://app.netlify.com/sites/authentik/deploys/6414eead9319330008bb46f0
😎 Deploy Preview https://deploy-preview-4995--authentik.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@codecov
Copy link

codecov bot commented Mar 17, 2023

Codecov Report

Patch coverage: 87.50% and project coverage change: -0.02 ⚠️

Comparison is base (e2d3a95) 92.78% compared to head (7f84d49) 92.75%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4995      +/-   ##
==========================================
- Coverage   92.78%   92.75%   -0.02%     
==========================================
  Files         501      501              
  Lines       25532    25538       +6     
==========================================
- Hits        23687    23686       -1     
- Misses       1845     1852       +7     
Flag Coverage Δ
e2e 52.70% <87.50%> (-0.03%) ⬇️
integration 26.51% <12.50%> (-<0.01%) ⬇️
unit 89.55% <87.50%> (-<0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
authentik/core/api/tokens.py 90.59% <80.00%> (-0.66%) ⬇️
authentik/blueprints/v1/importer.py 89.70% <100.00%> (+0.06%) ⬆️

... and 2 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@github-actions
Copy link
Contributor

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-blueprints-allow-special-fields-in-blueprint-1679093998-0716277
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-blueprints-allow-special-fields-in-blueprint-1679093998-0716277-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-blueprints-allow-special-fields-in-blueprint-1679093998-0716277

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-blueprints-allow-special-fields-in-blueprint-1679093998-0716277-arm64

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

@BeryJu BeryJu merged commit 97df784 into main Mar 17, 2023
45 of 47 checks passed
@BeryJu BeryJu deleted the blueprints/allow-special-fields-in-blueprint branch March 17, 2023 23:10
BeryJu added a commit that referenced this pull request Mar 18, 2023
closes #4717

Signed-off-by: Jens Langhammer <jens@goauthentik.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant