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

Planbuilder Authorization #2712

Merged
merged 1 commit into from
Nov 4, 2024
Merged

Planbuilder Authorization #2712

merged 1 commit into from
Nov 4, 2024

Conversation

Hydrocharged
Copy link
Contributor

@Hydrocharged Hydrocharged commented Oct 22, 2024

What's missing:

  • SHOW commands aren't in yet
  • information_schema doesn't restrict it's output yet
  • Need far more robust testing than what currently exists

I think SHOW and information_schema will probably have the same solution, which may be to continue doing what we were doing before. Besides that, pretty much every works according to our current tests (outside of the aforementioned missing items).

Copy link
Member

@zachmu zachmu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An interface might make more sense than a function pointer. And you definitely need to be getting more info from the builder to avoid doing unnecessary work.

But this seems like a big improvement over putting auth on every node type.

Can we get rid of PrivilegedDatabase as well? That thing has always been a pain.

@Hydrocharged Hydrocharged force-pushed the daylon/planbuilder-auth branch 2 times, most recently from cbb9ee1 to 66dbf92 Compare October 24, 2024 14:39
sql/plan/insert.go Outdated Show resolved Hide resolved
Copy link
Contributor

@max-hoffman max-hoffman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

directionally lgtm, i agree w/ zach re: deleting the old interface and validation analyzer rules

@Hydrocharged Hydrocharged changed the title POC planbuilder authorization Planbuilder Authorization Oct 30, 2024
Copy link
Contributor

@max-hoffman max-hoffman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly much more elegant, just the two main comments about deleting code and then whether auth on catalog would solve some of your TODOs

sql/analyzer/privileges.go Outdated Show resolved Hide resolved
sql/analyzer/optimization_rules_test.go Outdated Show resolved Hide resolved
sql/analyzer/triggers.go Outdated Show resolved Hide resolved
sql/plan/insert.go Outdated Show resolved Hide resolved
sql/planbuilder/builder.go Outdated Show resolved Hide resolved
Copy link
Member

@zachmu zachmu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

go.mod Outdated Show resolved Hide resolved
sql/analyzer/optimization_rules_test.go Outdated Show resolved Hide resolved
sql/mysql_db/privileged_database_provider.go Outdated Show resolved Hide resolved
@Hydrocharged
Copy link
Contributor Author

Hydrocharged commented Nov 4, 2024

@Hydrocharged
Copy link
Contributor Author

@Hydrocharged Hydrocharged merged commit e00c563 into main Nov 4, 2024
8 checks passed
@Hydrocharged Hydrocharged deleted the daylon/planbuilder-auth branch November 4, 2024 14:21
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

Successfully merging this pull request may close these issues.

3 participants