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

Custom Role names are not inserted into ROLES table automatically #2032

Open
markuzzi opened this issue Oct 4, 2024 · 3 comments
Open

Custom Role names are not inserted into ROLES table automatically #2032

markuzzi opened this issue Oct 4, 2024 · 3 comments

Comments

@markuzzi
Copy link
Contributor

markuzzi commented Oct 4, 2024

If the role names for CRUD are customized e.g. using env vars, FROST still creates the standard roles in the ROLES table (read, create, delete, update, admin).

I would have expected that FROST might create the customized role names instead.

@hylkevds
Copy link
Member

hylkevds commented Oct 4, 2024

Good point.
Though that feature is for when an existing users/rights database exists, in which case FROST doesn't need to create any data in those tables. If you're depending on FROST to generate placeholder data, why change the roles names?

We'd need to look into how to best pass those role names from environment variables to Liquibase.

@markuzzi
Copy link
Contributor Author

markuzzi commented Oct 6, 2024

Got your point. We change them, because in our setup, multiple components are using these role names. With your answer, let me rephrase my initial comment: It would be convenient, if FROST could generate the customized roles instead of the standard roles :-)

@markuzzi
Copy link
Contributor Author

markuzzi commented Oct 8, 2024

We switched to FROST default roles. So, this is not very urgent for us anymore 👍

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

No branches or pull requests

2 participants