-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
refactor: pass all properties to validate_parameters #21487
refactor: pass all properties to validate_parameters #21487
Conversation
c9a3d80
to
b488f5b
Compare
b488f5b
to
0d7b038
Compare
Codecov Report
@@ Coverage Diff @@
## master #21487 +/- ##
==========================================
- Coverage 66.79% 65.15% -1.65%
==========================================
Files 1799 1791 -8
Lines 68829 68587 -242
Branches 7314 7320 +6
==========================================
- Hits 45976 44689 -1287
- Misses 20974 22008 +1034
- Partials 1879 1890 +11
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
0d7b038
to
a4726e2
Compare
/testenv up |
@eschutho Ephemeral environment spinning up at http://34.219.255.3:8080. Credentials are |
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.
Awesome!
test the db connection form in ephemeral env, LGTM |
87cd1ce
to
986471e
Compare
986471e
to
aaeb7a5
Compare
Ephemeral environment shutdown and build artifacts deleted. |
(cherry picked from commit e98943e)
Some databases require values that aren't in the sqlalchemy uri in order to connect. I'm passing in all properties from the validate_params api into the db_engine_spec for validation, instead of just the
parameters
so that we can continue to keep the client side api structure as similar as possible to the db database model and not have to add the same values in both the root db payload and parameters in order to do validation. This is some pre-work for adding in the databricks form that requires http_path from extras for connection.Hopefully this change will help clarify the difference between parameters, and when something is a parameter in the db model and when it's not.
I'm also adding the driver to the db model, because as per @betodealmeida's change in #21171 if an engine can have multiple drivers, like databricks, we're going to need to pass that value in from the client side when creating/editing a db in order for us to find the correct db_engine_spec.
TESTING INSTRUCTIONS
Database creation with the new forms should work as expected.
ADDITIONAL INFORMATION