Closed rndquu closed 7 months ago
Can you do a time estimate on this?
/start
Deadline | Tue, Mar 12, 11:24 AM UTC |
Registered Wallet | 0x0fC1b909ba9265A846b82CF4CE352fc3e7EeB2ED |
/wallet 0x0000...0000
if you want to update your registered payment wallet address.Important notes:
The column rights features is still in Alpha through the Supabase Dashboard, so to be manipulated with caution. Secondly:
Changes to column privileges will not be reflected in migrations when running supabase db diff.
Column privileges are not supported in the current version of the Supabase CLI.
You will need to manually apply these changes to your database.
Third, the changes also impact audit.ubq
project, since it also pulls data from the db (reads only).
You will need to manually apply these changes to your database.
By "manually" it is meant to set priviliges via supabase's dashboard UI, right?
Third, the changes also impact audit.ubq project, since it also pulls data from the db (reads only).
As far as I remember https://audit.ubq.fi/ needs access only to the permits
table so it seems to be ok to allow https://audit.ubq.fi/ read access to the permits
table.
Yes audit is good with read only permissions on permits
so that's all good, if you can think of any project that is also linked to the db that we should test please let me know.
Manually means that if we run a diff
these changes won't be contained in the migration file. So any change done through the UI will be lost when it comes to CLS and migrations, which I mention to avoid mistakes later. Otherwise it works fine so far.
@pavlovcik @rndquu Is the pavlovcik's supabase DB
also used for the bot in production? Or is there a different instance for this? Also asking because the migrations in this repo are not matching.
So any change done through the UI will be lost when it comes to CLS and migrations, which I mention to avoid mistakes later.
The best thing we can do in this case is to describe the required RLS/CLS setup in the README file
Is the pavlovcik's supabase DB also used for the bot in production?
Yes
Also asking because the migrations in this repo are not matching.
Yes, migrations in the current repo are deprecated. Migrations for the kernel are not yet created and I'm in doubt if we need ones since all of the kernel plugins will have their own DBs so I'm not sure what exactly we need to store in the kernel's DB.
So the wfzpewmlyiozupulbuur
Supabase project has been updated as such:
All the other tables have no rules so are accessible only by service key / admin.
The reason why all these table need the read-only is to satisfy audit
that calls
const { data: permits } = await supabase
.from("permits")
.select("*, locations(*), users(*, wallets(*)), tokens(*)")
.in("locations.issue_id", issueIds)
.not("locations", "is", null);
To retrieve permits and their associated data. If we don't allow the read, all the data returned is empty within the permit.
For updates, the column transaction is the only one that can be modified by a user
! action has an uncaught error
+ Evaluating results. Please wait...
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 1 | 0.8 |
Review | Comment | 2 | 1.9 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Can you do a time estimate on this?... | 0.8 | 0.27 | 0.8 |
I don't know enough about migrations to understand this pull wel... | 1.3 | 0.2 | 1.3 |
> Since we gonna have one DB per module it shall be irrelevant s... | 0.6 | 0.71 | 0.6 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Task | 1 | 200 |
Issue | Comment | 4 | 0 |
Issue | Comment | 4 | 45.2 |
Review | Comment | 2 | 13.5 |
Review | Comment | 2 | 13.5 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 18.6 |
Issue | Comment | 2 | 27.4 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Right now we're using a pavlovcik's supabase DB instance with di... | 18.6a: count: 4 score: "4" words: 4 li: count: 2 score: "2" words: 76 code: count: 2 score: "2" words: 4 | 1 | 18.6 |
> You will need to manually apply these changes to your database... | 11.6code: count: 2 score: "2" words: 2 | 0.66 | 11.6 |
> So any change done through the UI will be lost when it comes t... | 15.8a: count: 1 score: "1" words: 1 | 0.74 | 15.8 |
View | Contribution | Count | Reward |
---|---|---|---|
Review | Comment | 1 | 1 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Sorry, I didn't know you were waiting for me... | 1 | 0.12 | 1 |
Right now we're using a pavlovcik's supabase DB instance with disabled RLS
What should be done:
permits.transaction
field can only be updated by an authorized user who matchespermits.beneficiary_id
(related comment)