Conversation
|
🤖 Hey ! The @cpn-console/keycloak-plugin (v2.1.0) package already exists on npm but the source code has changed, you should consider updating the package version. The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc... |
|
@StephaneTrebel Par complet hasard, ca te parle ce probleme ? J'arrive pas a faire le liens entre "info" de plugin a la table ProjectPlugin, y a un soucis d'interconnection entre la config et la data mais je vois pas ou c'est branche dans le code. |
|
🤖 Hey ! The security scan report for the current pull request is available here. |
For some reasons, the config is never passed down to the plugins hooks. Apparently the config is provided via the adminPlugin table of the database but is empty most of the time so for the moment let's just add default and fix the problem properly later. Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr>
|
0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (71.10% Estimated after merge)
| try { | ||
| const kcClient = await getkcClient() | ||
| const projectName = project.slug | ||
| const purgeEnabled = config.keycloak?.purge === ENABLED |
There was a problem hiding this comment.
praise: Oui, bien vu 👍
|
Merged in #1913 |
2 participants
For some reasons, the config is never passed down to the plugins hooks. Apparently the config is provided via the adminPlugin table of the database but is empty most of the time so for the moment let's just add default and fix the problem properly later.
Signed-off-by: William Phetsinorath william.phetsinorath-open@interieur.gouv.fr
Stack created with Sapling. Best reviewed with ReviewStack.