Skip to content

Conversation

@overheadhunter
Copy link
Member

@overheadhunter overheadhunter commented Oct 27, 2021

The frontend is now capable to read app configuration from the /setup resource.

Doing so, it detects whether setup is required and redirects to a wizard. Currently it only contains Keycloak-related stuff, but may be extended later.

By configuring Keycloak dynamically, we no longer rely on assumptions hard-coded in realm configuration files, which allows to remove them and switch to Quarkus Dev Services for Keycloak provisioning during development.

@infeo infeo self-requested a review October 28, 2021 14:15
Copy link
Member

@infeo infeo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately i cannot say a lot about the typescript part, but i tested it in a run and it works.

@@ -1,4 +1,51 @@
<template>
<!-- Notification for successfully creation of a realm -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not remove directly and just reference the git commit where the old state can be taken from?

@overheadhunter overheadhunter merged commit 00bc266 into develop Nov 2, 2021
@overheadhunter overheadhunter deleted the feature/setup-keycloak-realm branch November 3, 2021 08:59
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.

3 participants