Fix destination-exasol build and CatalogDefinition generation#23321
Fix destination-exasol build and CatalogDefinition generation#23321Evan Tahler (evantahler) merged 8 commits intomasterfrom
destination-exasol build and CatalogDefinition generation#23321Conversation
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-exasol |
0.1.1 |
✅ | ✅ |
- 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. |
destination-exasol build
|
/test connector=connectors/destination-exasol
Build PassedTest summary info: |
|
Debugging:
|
| args new File(project(":airbyte-config:init").projectDir, '/src/main/resources/seed') | ||
| } | ||
|
|
||
| task downloadCombinedConnectorCatalog(type: JavaExec, dependsOn: compileJava) { |
There was a problem hiding this comment.
Pedro S. Lopez (@pedroslopez) Sanity check, we can delete all the download logic in connectors. Correct?
There was a problem hiding this comment.
Correct!
Ben Church (bnchrch)
left a comment
There was a problem hiding this comment.
Evan Tahler (@evantahler) Should be good to merge 👍
|
Thank you Ben Church (@bnchrch) and Pedro S. Lopez (@pedroslopez)! |
|
/publish connector=connectors/destination-exasol
if you have connectors that successfully published but failed definition generation, follow step 4 here |
destination-exasol builddestination-exasol build and CatalogDefinition generation
Fixes the
destination-exasolbuild (added via #21200). Lots of stuff changed when we ripped apart our monorepo 😅Tested locally via