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

feat: create function for get_sqla_engine with context #21790

Merged
merged 12 commits into from
Oct 25, 2022

Conversation

hughhhh
Copy link
Member

@hughhhh hughhhh commented Oct 12, 2022

SUMMARY

First step in allowing enabling ssh tunneling by allowing the get_sqla_engine function to be a context manager. This will allow us to add logic before and after yielding the engine for spinning up and tearing down the tunnel on each connection.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@codecov
Copy link

codecov bot commented Oct 12, 2022

Codecov Report

Merging #21790 (63d4a9c) into master (8f4415b) will increase coverage by 0.87%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master   #21790      +/-   ##
==========================================
+ Coverage   66.18%   67.06%   +0.87%     
==========================================
  Files        1805     1805              
  Lines       69066    69416     +350     
  Branches     7369     7369              
==========================================
+ Hits        45712    46554     +842     
+ Misses      21448    20955     -493     
- Partials     1906     1907       +1     
Flag Coverage Δ
hive 53.24% <71.42%> (+0.32%) ⬆️
javascript 53.33% <ø> (-0.01%) ⬇️
mysql 78.50% <71.42%> (?)
postgres 78.57% <71.42%> (?)
presto 53.14% <71.42%> (+0.32%) ⬆️
python 81.59% <71.42%> (+1.67%) ⬆️
sqlite 77.04% <71.42%> (+0.14%) ⬆️
unit 51.36% <42.85%> (+0.29%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
superset/models/core.py 89.79% <71.42%> (+1.08%) ⬆️
...ols/MetricControl/AdhocMetricEditPopover/index.jsx 74.46% <0.00%> (-1.07%) ⬇️
superset/examples/tabbed_dashboard.py 0.00% <0.00%> (ø)
superset/initialization/__init__.py 91.50% <0.00%> (+0.04%) ⬆️
superset/db_engine_specs/base.py 89.69% <0.00%> (+0.15%) ⬆️
superset/datasets/schemas.py 97.75% <0.00%> (+0.36%) ⬆️
superset/views/core.py 76.06% <0.00%> (+0.45%) ⬆️
superset/common/query_object.py 94.38% <0.00%> (+0.51%) ⬆️
superset/connectors/sqla/models.py 91.01% <0.00%> (+0.51%) ⬆️
superset/commands/importers/v1/utils.py 93.50% <0.00%> (+1.29%) ⬆️
... and 32 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@hughhhh hughhhh marked this pull request as ready for review October 14, 2022 17:14
@pull-request-size pull-request-size bot added size/S and removed size/M labels Oct 17, 2022
@pull-request-size pull-request-size bot added size/L and removed size/S labels Oct 17, 2022
@hughhhh hughhhh force-pushed the ssh-tunnel-refactor-get-sqla-engine branch 2 times, most recently from d53079d to 03029dd Compare October 19, 2022 23:56
@@ -362,6 +362,18 @@ def get_effective_user(self, object_url: URL) -> Optional[str]:
else None
)

@contextmanager
def get_sqla_engine_with_context(

Choose a reason for hiding this comment

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

What is the difference between having this new get_sqla_engine_with_context with the decorator VS using it in our existing get_sqla_engine ? I Mean, couldn't we just use the existing one and make use or not of the new functionality the decorator brings when needed? or would that mean changing a ton of places where the get_sqla_engine is being used right now?

Copy link
Member

Choose a reason for hiding this comment

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

For now there's no difference, but Hugh is planning to add support for SSH tunneling, which would require a setup phase before the engine is created, and a teardown after. In order for the SSH tunnel to work everywhere we will need to replace all existing calls with the new context manager.

Choose a reason for hiding this comment

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

Oh ok ok, makes sense then 😎 thanks!

db = make_url(model.get_sqla_engine().url).database
self.assertEqual("prod", db)
with model.get_sqla_engine_with_context() as engine:
db = make_url(engine.url).database
Copy link
Member

@Antonio-RiveroMartnez Antonio-RiveroMartnez Oct 20, 2022

Choose a reason for hiding this comment

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

I see we have this make_url_safe here: superset/databases/utils.py, would that serve the same purpose? If so, can we change to that one or must we keep using this?

Copy link
Member

Choose a reason for hiding this comment

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

make_url_safe prevents password from showing up in the logs when make_url fails for some reason. It should always be used in production, but in the tests it's fine to use make_url instead.

Choose a reason for hiding this comment

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

Good to know 👍 Thanks!

Copy link
Member

@betodealmeida betodealmeida left a comment

Choose a reason for hiding this comment

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

What's the plan for modifying the files in superset/?

Comment on lines 164 to 182
perm_data = ROLE_TABLES_PERM_DATA.copy()
perm_data["database"][0]["schema"][0]["name"] = schema

response = self.client.post(
"/superset/override_role_permissions/",
data=json.dumps(perm_data),
content_type="application/json",
)
self.assertEqual(201, response.status_code)
response = self.client.post(
"/superset/override_role_permissions/",
data=json.dumps(perm_data),
content_type="application/json",
)
self.assertEqual(201, response.status_code)

updated_override_me = security_manager.find_role("override_me")
self.assertEqual(1, len(updated_override_me.permissions))
birth_names = self.get_table(name="birth_names")
self.assertEqual(
birth_names.perm, updated_override_me.permissions[0].view_menu.name
)
self.assertEqual(
"datasource_access", updated_override_me.permissions[0].permission.name
)
updated_override_me = security_manager.find_role("override_me")
self.assertEqual(1, len(updated_override_me.permissions))
birth_names = self.get_table(name="birth_names")
self.assertEqual(
birth_names.perm, updated_override_me.permissions[0].view_menu.name
)
self.assertEqual(
"datasource_access", updated_override_me.permissions[0].permission.name
)
Copy link
Member

Choose a reason for hiding this comment

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

I think this doesn't have to be inside the context manager.

Comment on lines 192 to 218
override_me = security_manager.find_role("override_me")
override_me.permissions.append(
security_manager.find_permission_view_menu(
view_menu_name=self.get_table(name="energy_usage").perm,
permission_name="datasource_access",
)
)
)
db.session.flush()
db.session.flush()

perm_data = ROLE_TABLES_PERM_DATA.copy()
perm_data["database"][0]["schema"][0]["name"] = schema
perm_data = ROLE_TABLES_PERM_DATA.copy()
perm_data["database"][0]["schema"][0]["name"] = schema

response = self.client.post(
"/superset/override_role_permissions/",
data=json.dumps(perm_data),
content_type="application/json",
)
self.assertEqual(201, response.status_code)
updated_override_me = security_manager.find_role("override_me")
self.assertEqual(1, len(updated_override_me.permissions))
birth_names = self.get_table(name="birth_names")
self.assertEqual(
birth_names.perm, updated_override_me.permissions[0].view_menu.name
)
self.assertEqual(
"datasource_access", updated_override_me.permissions[0].permission.name
)
response = self.client.post(
"/superset/override_role_permissions/",
data=json.dumps(perm_data),
content_type="application/json",
)
self.assertEqual(201, response.status_code)
updated_override_me = security_manager.find_role("override_me")
self.assertEqual(1, len(updated_override_me.permissions))
birth_names = self.get_table(name="birth_names")
self.assertEqual(
birth_names.perm, updated_override_me.permissions[0].view_menu.name
)
self.assertEqual(
"datasource_access", updated_override_me.permissions[0].permission.name
)
Copy link
Member

Choose a reason for hiding this comment

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

Same here.

@@ -362,6 +362,18 @@ def get_effective_user(self, object_url: URL) -> Optional[str]:
else None
)

@contextmanager
def get_sqla_engine_with_context(
Copy link
Member

Choose a reason for hiding this comment

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

Eventually I think we want to rename this to get_sqla_engine, since we want this to be the one and only way to create an engine.

with database.get_sqla_engine_with_context() as engine:
engine.execute("CREATE TABLE test_table AS SELECT 1 as first, 2 as second")
engine.execute("INSERT INTO test_table (first, second) VALUES (1, 2)")
engine.execute("INSERT INTO test_table (first, second) VALUES (3, 4)")

yield db.session
database.get_sqla_engine().execute("DROP TABLE test_table")
Copy link
Member

Choose a reason for hiding this comment

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

Here too?

@hughhhh
Copy link
Member Author

hughhhh commented Oct 21, 2022

What's the plan for modifying the files in superset/?

  1. Create get_sqla_engine_with_context() function and switch out places in our testing suite that straight forward (this PR)
  2. Update get_sqla_engine() to _get_sqla_engine() making it a private function and switch out all remaining places that get_sqla_engine() to use get_sqla_engine_with_context()
    • open to changing the name to get_sqla_engine for the contextmanager and then change the name of the original function to something else

I initially wanted to take incremental approach with 1 first to verify the get_sqla_engine_with_context won't break things then have a follow up PR that will close up the remaining work let me know what you think

@betodealmeida

Copy link
Member

@Antonio-RiveroMartnez Antonio-RiveroMartnez left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Member

@betodealmeida betodealmeida left a comment

Choose a reason for hiding this comment

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

Looks great!

@hughhhh hughhhh merged commit 7600da8 into master Oct 25, 2022
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 2.1.0 and removed 🚢 2.1.3 labels Mar 13, 2024
@mistercrunch mistercrunch deleted the ssh-tunnel-refactor-get-sqla-engine branch March 26, 2024 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/L 🚢 2.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants