You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 :-)
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.
The text was updated successfully, but these errors were encountered: