Repository navigation
Remove SSL toggle for source-postgres in OSS - #24859
Conversation
|
/test connector=connectors/source-postgres
Build FailedTest summary info: |
Affected Connector ReportNOTE
|
| Connector | Version | Changelog | Publish |
|---|---|---|---|
source-alloydb |
2.0.19 |
✅ | ✅ |
source-alloydb-strict-encrypt |
2.0.19 |
🔵 (ignored) |
🔵 (ignored) |
source-postgres-strict-encrypt |
2.0.20 |
🔵 (ignored) |
🔵 (ignored) |
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Destinations (0)
| Connector | Version | Changelog | Publish |
|---|
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Other Modules (0)
Actionable Items
(click to expand)
| Category | Status | Actionable Item |
|---|---|---|
| Version | ❌ mismatch |
The version of the connector is different from its normal variant. Please bump the version of the connector. |
| ⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
|
| Changelog | ⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
| ❌ changelog missing |
There is no chnagelog for the current version of the connector. If you are the author of the current version, please add a changelog. | |
| Publish | ⚠ not in seed |
The connector is not in the seed file (e.g. source_definitions.yaml), so its publication status cannot be checked. This can be normal (e.g. some connectors are cloud-specific, and only listed in the cloud seed file). Please double-check to make sure that it is not a bug. |
| ❌ diff seed version |
The connector exists in the seed file, but the latest version is not listed there. This usually means that the latest version is not published. Please use the /publish command to publish the latest version. |
|
/test connector=connectors/source-postgres
Build FailedTest summary info: |
539b9c7 to
df2a642
Compare
|
/test connector=connectors/source-postgres
|
2466ca2 to
144f9a6
Compare
|
/test connector=connectors/source-postgres
Build PassedTest summary info: |
6f4271e to
e6a98ee
Compare
|
/test connector=connectors/source-postgres |
|
/test connector=connectors/source-postgres-strict-encrypt
Build PassedTest summary info: |
There was a problem hiding this comment.
Does it work without PARAM_SSL?
I think it should but to verify that it's not needed on either disabled or enabled modes
There was a problem hiding this comment.
Just manually verified with a successful sync without SSL.
There was a problem hiding this comment.
Why exactly are we removing this again?
There was a problem hiding this comment.
The toggle is logically redundant.
Setting ssl mode to disabled has the same effect of setting this toggle to false.
|
Also in source-postgres-strict-encrypt I think we're removing this ssl toggle programmatically. |
|
I'm not working on this anymore, but I agree that since this field is being removed from the spec, then this line that removes it for strict encrypt specifically should be removed: |
2a60551 to
3a3ec86
Compare
|
/test connector=connectors/source-postgres
Build PassedTest summary info: |
|
/test connector=connectors/source-postgres-strict-encrypt
Build PassedTest summary info: |
Updated expected_spec to match spec
…" from properties
81d8db7 to
1a12e87
Compare
|
/test connector=connectors/source-postgres
Build PassedTest summary info: |
|
/publish connector=connectors/source-postgres
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/publish connector=connectors/source-postgres-strict-encrypt auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
* Basic removal * Removed SSL key static variables in PostgresSource Updated expected_spec to match spec * Removed autocommit for SelectDB * Removed the line in PostgresSourceStrictEncrypt that removed "SSL_KEY" from properties * Revert "Removed autocommit for SelectDB" This reverts commit 14ff20d. * bumped Dockerfile versions and updated changelog * Reverted removal of SSL key from the JDBC Connection query * Removed extraneous keys * auto-bump connector version --------- Co-authored-by: Rodi Reich Zilberman <867491+rodireich@users.noreply.github.com> Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
What
Issue
Currently for DB sources that have a strict encrypt variant, the connection will fail even if the user has selected, for example,
verify-caand filled out all relevant information. We want to mitigate confusion by having thessl_modebe the sole source of truth for enabling/disabling SSL connection.Solution
Remove the ssl key from
spec.jsonforsource-postgresand rely onssl_modekey as the source of truth. This also entails removing any reference to the ssl key in the protocol. Note: this needs to be backwards compatible with historical config file. We will need to ignore the ssl key and only honorssl_mode.Aside from automated tests, manual tests conducted: