* Init: New Source: SpaceX API * Chore: Removed duplicate and unwanted files * fix: Reconfigured schema and matched the read records. chore: Acceptance test run and results passed without errors * chore: Added documentation, updated airbyte docs specific to the connector * fix conflict * Chore: delete unwanted files * chore: Created bootstrap.md * chore: Update doc url, removed unwanted files * fix: Fixed schema after crosscheck with several schema validators * fix: resolved .vscode setting conflict, resolved merge conflict * feat: Added support for all endpoints * chore: updated documentation * feat: changes to stream path to accept options and id * fix: Resolve coomments * chore: resolved comments * chore: Delete unwanted files * chore: Update Readme.md after resolving merge conflict * update connector * add spacex api to source def * run format * add schemaloader * auto-bump connector version Co-authored-by: marcosmarxm <marcosmarxm@gmail.com> Co-authored-by: Marcos Marx <marcosmarxm@users.noreply.github.com> Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
1.0 KiB
1.0 KiB
SpaceX-API
The connector uses the v4 API documented here: https://github.com/r-spacex/SpaceX-API . It is straightforward HTTP REST API with no authentication.
Dummy API key
Api key is mandate for this connector to work as it could be used in future enhancements. Just pass any dummy api key for establishing the connection. Example:123
Implementation details
Setup guide
Step 1: Set up SpaceX connection
- Have a dummy API key (Example: 12345)
- A specific id (If specific info is needed)
Step 2: Generate schema for the endpoint
Custom schema is generated and tested with different IDs
Step 3: Spec, Secrets, and connector yaml files are configured with reference to the Airbyte documentation.
In a nutshell:
- Navigate to the Airbyte Open Source dashboard.
- Set the name for your source.
- Enter your
api_key. - Enter your
idif needed. (Optional) - Click Set up source.
- We use only GET methods, all endpoints are straightforward. We emit what we receive as HTTP response.