-
Notifications
You must be signed in to change notification settings - Fork 0
AuthZ for Payment Tiers #43
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
Conversation
await db.update(users).set({ tier }).where(eq(users.hidraId, hidraId)); | ||
|
||
console.log( | ||
`${tier.toUpperCase()} Subscription Tier set for User: ${hidraId}`, |
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.
bunch of console logs in this file that may leak Id's. If this isn't a problem, disregard.
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.
Well, this is all on the server, so doesn't leak to the public. But ofc can always remove logging! hidraId
I feel like is fine to display in logs here. Going to move forward and get this merged as is, but will tag @coopbri here for visibility to get his thoughts as well! Happy to push a hotfix later if we want to remove the logs
Description
Task link: https://linear.app/omnidev/issue/OMNI-192/implement-authz-based-on-payment-tier
Added
tier
to the graphql context through thecurrentUser
object. Updated the RBAC plugins for organizations and projects to include restrictions based on the current user's subscription.Important
Test with this App repo PR.
Test Steps
tier
column is not available for user mutations through the API