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

Use API database group-project association instead of keycloak attributes #97

Closed
shreddedbacon opened this issue Mar 15, 2024 · 0 comments · Fixed by #114
Closed

Use API database group-project association instead of keycloak attributes #97

shreddedbacon opened this issue Mar 15, 2024 · 0 comments · Fixed by #114

Comments

@shreddedbacon
Copy link
Member

Now that uselagoon/lagoon#3612 has been merged, opensearch-sync will need to be updated to consume the group-project associations the same way that the API does as the attributes in keycloak will be stop being populated in a future release of Lagoon.

This means that this support is not required to be done in time for the Lagoon v2.18.0 release, but should be usable prior to v2.20.0 when the attributes will likely be removed.

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 a pull request may close this issue.

1 participant