Destination connector for teradata vantage (rebased community PR) #21160
Conversation
octavia-squidington-iv
added
area/connectors
Affected Connector ReportNOTE
|
| Connector | Version | Changelog | Publish |
|---|
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Destinations (1)
| Connector | Version | Changelog | Publish |
|---|---|---|---|
destination-teradata |
0.1.0 |
✅ | ✅ |
- 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. |
grishick
force-pushed
the
greg/teradata-vantage
branch
from
855d194 to
26cfb8d
Compare
|
/test connector=connectors/destination-teradata
Build PassedTest summary info: |
|
/publish connector=connectors/destination-teradata
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/publish connector=connectors/destination-teradata
if you have connectors that successfully published but failed definition generation, follow step 4 here |
grishick
force-pushed
the
greg/teradata-vantage
branch
from
26cfb8d to
5d1c0ff
Compare
|
/approve-and-merge reason=”These changes were already approved in the original PR #20428" |
|
This is really good |
…1160) * Destination connector for teradata vantage is implemented * add teradata destination to seed yaml * Add teradata destination to specs seed file Co-authored-by: Satish Chinthanippu <satishchinthanippu@gmail.com>
What
Rebased version of this PR: #20428