-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 config-based docs accessible through direct link #15662
Conversation
@@ -3,7 +3,7 @@ | |||
:warning: This framework is in alpha stage. Support is not in production and is available only to select users. :warning: | |||
|
|||
The goal of this document is to give enough technical specifics to understand how config-based connectors work. | |||
When you're ready to start building a connector, you can start with [the tutorial](../../../config-based/tutorial/0-getting-started.md) or dive into the [reference documentation](https://airbyte-cdk.readthedocs.io/en/latest/api/airbyte_cdk.sources.declarative.html) | |||
When you're ready to start building a connector, you can start with [the tutorial](./tutorial/0-getting-started.md) or dive into the [reference documentation](https://airbyte-cdk.readthedocs.io/en/latest/api/airbyte_cdk.sources.declarative.html) |
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.
fix link
@@ -90,7 +90,7 @@ The connector will now always read data for the start date, which is not exactly | |||
Instead, we would like to iterate over all the dates between the start_date and today and read data for each day. | |||
|
|||
We can do this by adding a `DatetimeStreamSlicer` to the connector definition, and update the `path` to point to the stream_slice's `start_date`: | |||
More details on the stream slicers can be found [here](./link-to-stream-slicers.md) <FIXME: need to fix links> | |||
More details on the stream slicers can be found [here](../stream-slicers.md) <FIXME: need to fix links> |
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.
fix link
- [Stream slices](../../cdk-python/stream-slices.md) |
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.
fix link
@@ -39,7 +39,7 @@ $ python -m pytest integration_tests -p integration_tests.acceptance | |||
|
|||
Next, we'll add the connector to the [Airbyte platform](https://docs.airbyte.com/connector-development/tutorials/cdk-tutorial-python-http/use-connector-in-airbyte). | |||
|
|||
See your [Contributiong guide]() on how to get started releasing your connector. | |||
See your [Contributiong guide](../../../contributing-to-airbyte/README.md) on how to get started releasing your connector. |
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.
fix link
@@ -62,7 +62,6 @@ const config = { | |||
sidebarPath: require.resolve('./sidebars.js'), | |||
editUrl: 'https://github.com/airbytehq/airbyte/blob/master/docs', | |||
path: '../docs', | |||
exclude: ['**/connector-development/config-based/**'] |
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.
include /connector-development/config-based/ to the build, but not to the sidebar
@@ -137,7 +137,7 @@ In this example, outer.inner.k2 will evaluate to "MyKey is MyValue" | |||
Strings can contain references to previously defined values. | |||
The parser will dereference these values to produce a complete ConnectionDefinition | |||
|
|||
References can be defined using a *ref(<arg>) string. |
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.
i think docusaurus was interpreting the <> as an html directive. the build step stopped complaining after changing to {arg}
|
||
These tests currently all live in [airbyte-webapp-e2e-tests](../.././airbyte-webapp-e2e-tests) | ||
These tests currently all live in [airbyte-webapp-e2e-tests](https://github.com/airbytehq/airbyte/airbyte-webapp-e2e-tests) |
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.
link to github because airbyte-webapp-e2e-tests
isn't part of the docs
@@ -101,18 +102,18 @@ We split Acceptance Tests into 2 different test suites: | |||
* Platform Acceptance Tests: These tests are a coarse test to sanity check that each major feature in the platform. They are run with the following command: `SUB_BUILD=PLATFORM ./gradlew :airbyte-tests:acceptanceTests`. These tests expect to find a local version of Airbyte running. For testing the docker version start Airbyte locally. For an example, see the [acceptance_test script](../../tools/bin/acceptance_test.sh) that is used by the CI. For Kubernetes, see the [accetance_test_kube script](../../tools/bin/acceptance_test_kube.sh) that is used by the CI. | |||
* Migration Acceptance Tests: These tests make sure the end-to-end process of migrating from one version of Airbyte to the next works. These tests are run with the following command: `SUB_BUILD=PLATFORM ./gradlew :airbyte-tests:automaticMigrationAcceptanceTest --scan`. These tests do not expect there to be a separate deployment of Airbyte running. | |||
|
|||
These tests currently all live in [airbyte-tests](../.././airbyte-tests) | |||
These tests currently all live in [airbyte-tests](https://github.com/airbytehq/airbyte/airbyte-tests) |
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.
link to github because airbyte-tests
isn't included in the docs
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.
@ryankfu FYI
* fix broken links * include config-based * throw on broken links * fix link * reset
What
Add low-code documentation to https://docs.airbyte.com/connector-development/config-based without adding a link to it in the sidebar.
This will allow user research to use a direct link to the docs without explicitly making it available for the general public.
How
Recommended reading order
docusaurus/docusaurus.config.js
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changesTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.