-
Notifications
You must be signed in to change notification settings - Fork 0
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
docs: update README with detailed instructions for role and RLS policy management #8
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this improved README. A couple of suggestions and questions
README.md
Outdated
|
||
## Creating RLS policies | ||
|
||
The process is similar to the one above for creating roles. The `group key` and `clause` are the important bits here and should be configured accordingly. They determine what level of access the role will have. For example, the clause 'county_name' = '{{county_name}}' will allow the role to access data from the specified county. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: Add an example JSON payload for how to create RLS Policy
README.md
Outdated
} | ||
``` | ||
|
||
Next, update the permissions for the roles. Subsequent roles for individual types will be copied off of these `base` roles. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: should we describe how to update the permissions for the roles on the UI ? Or via API ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The API for now. Doing it via the UI can introduce unwanted changes due to how the permissions UX is presented.
Co-authored-by: Ben Kiarie <[email protected]>
Co-authored-by: Ben Kiarie <[email protected]>
Co-authored-by: Ben Kiarie <[email protected]>
Co-authored-by: Ben Kiarie <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more suggestion. I thought I had shared it yesterday.
Thank you for adding the json for roles and rls policies.
|
||
Clone the repository and install the dependencies: | ||
```bash | ||
npm install | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clone the repository and install the dependencies: | |
```bash | |
npm install | |
``` | |
1. Clone the repository. | |
2. install the dependencies: `npm install` | |
3. Create a `data` folder in the root of the repository | |
3. Add your csv file to the data folder, refer to the `./src/template.csv` for a sample. | |
2. Define your environment variables - make a copy of `.env.template` and rename to `.env` |
No description provided.