Destination MotherDuck: Finer grained custom user agent

[Donny Peeters (Donnype)]

IMPORTANT: I set the version to 0.1.28 because I expect #70438 will be merged first, so hence this PR is a draft.

What

This PR makes the custom_user_agent include the AIRBYTE_VERSION and AIRBYTE_EDITION per the MotherDuck user agent specification. Note that AIRBYTE_EDITION is a bit of a shot in the dark as there are no docs on this environment variable, but locally I found it to be set to COMMUNITY, so I expect the Airbyte cloud to specify something else here.

How

This reads out the env when instantiating the MotherDuckConfig.

Review guide

User Impact

This should have no impact on users, but helps MotherDuck help users pinpoint issues with their integration.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

[github-actions]

👋 Welcome to Airbyte!

Thank you for your contribution from Donnype/airbyte! We're excited to have you in the Airbyte community.

Helpful Resources

• PR Guidelines: Check our guidelines for contributions.
• Breaking Changes Guide: Guide to breaking changes, migration guides, and upgrade deadlines.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
• /run-connector-tests - Runs connector tests.
• /run-cat-tests - Runs CAT tests.
• /run-live-tests - Runs live tests for the modified connector(s).
• /run-regression-tests - Runs regression tests for the modified connector(s).
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
• /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-dev.{git-sha}) for all modified connectors in the PR.

If you have any questions, feel free to ask in the PR comments or join our Slack community.

Tips for Working with CI

1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
   • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

📝 Edit this welcome message.

[Danylo Jablonski (DanyloGL)]

/run-connector-tests

Connector CI Tests Started

These tests will leverage Airbyte's integration test credentials.

Check job output.
✅ Connector CI Tests job completed successfully. See logs for details.

[Jim Ruppert (jimruppert)]

Donny Peeters (@Donnype) The connector has moved on since this was opened (0.2.1 here vs 0.2.5 on master) and the branch now conflicts. Happy to look again at a rebased version.

We are closing a number of PRs that may be stale or redundant as a first step towards improved handling of PRs. If you believe this is currently still an issue, please comment and we'll reopen.

[Donny Peeters (Donnype)]

Jim Ruppert (@jimruppert) Done: #84292