-
Notifications
You must be signed in to change notification settings - Fork 4.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
Make error more descriptive in case of no encryption state #17299
Make error more descriptive in case of no encryption state #17299
Conversation
/test connector=connectors/source-mysql-strict-encrypt
Build FailedTest summary info:
|
/test connector=connectors/source-postgres-strict-encrypt
Build PassedTest summary info:
|
/test connector=connectors/source-mysql-strict-encrypt
Build FailedTest summary info:
|
…rict-encrypt-connector-when-configuring-unsecured-connection
…connector-when-configuring-unsecured-connection' of github.com:airbytehq/airbyte into 16664-improve-user-experience-for-cloud-strict-encrypt-connector-when-configuring-unsecured-connection
/test connector=connectors/source-mysql-strict-encrypt
Build PassedTest summary info:
|
NOTE
|
/publish connector=connectors/source-postgres,connectors/source-mysql,connectors/destination-postgres
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-postgres-strict-encrypt,connectors/source-mysql-strict-encrypt,connectors/destination-postgres-strict-encrypt auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-postgres,connectors/source-mysql,connectors/destination-postgres run-tests=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
…#17299) * Make error more descriptive in case of no encryption state * Fix failing test * Change error message on strict-encrypt postgres destination as well. Fix failing test * update versions and changelogs * auto-bump connector version [ci skip] * auto-bump connector version [ci skip] * auto-bump connector version [ci skip] Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
…#17299) * Make error more descriptive in case of no encryption state * Fix failing test * Change error message on strict-encrypt postgres destination as well. Fix failing test * update versions and changelogs * auto-bump connector version [ci skip] * auto-bump connector version [ci skip] * auto-bump connector version [ci skip] Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
What
Improve error wording:
