f488a04b69
## What Regenerates platform documentation version 2.0 from the latest Next (unreleased) version. This publishes all recent documentation updates that have been made to the Next version as the stable 2.0 release. Requested by Ian Alton (@ian-at-airbyte) via Slack thread: https://airbytehq-team.slack.com/archives/D08FX8EC9L0/p1760747793195139?thread_ts=1760747793.195139 Link to Devin session: https://app.devin.ai/sessions/edbc303b017445de9731080a55c04586 ## How 1. Deleted the existing `version-2.0` directory from `platform_versioned_docs/` 2. Deleted the `version-2.0-sidebars.json` from `platform_versioned_sidebars/` 3. Temporarily removed `"2.0"` from `platform_versions.json` 4. Ran `pnpm docusaurus docs:version:platform 2.0` to regenerate version 2.0 from the current Next version 5. Verified the build succeeds locally ## Review guide 1. **New content**: `platform_versioned_docs/version-2.0/understanding-airbyte/cdc-best-practices.md` - Comprehensive new CDC configuration best practices guide. Review for technical accuracy. 2. **Sidebar changes**: `platform_versioned_sidebars/version-2.0-sidebars.json` - CDC content reorganized under "Sync Modes" section. Verify navigation makes sense. 3. **Terminology updates** throughout various files: - "Airbyte Open Source" → "Core" - "Cloud Teams" → "Cloud Pro" - "Self-Managed Community" → "Core" - Verify these align with actual product naming conventions 4. **Content improvements** in access management, API documentation, connector development, enterprise setup, and quickstart guides ## User Impact Users viewing the version 2.0 platform documentation will see the latest content updates, including: - New comprehensive CDC best practices documentation - Updated terminology reflecting current product names - Improved clarity and accuracy throughout documentation - Better organization of CDC-related content No negative side effects expected - this is a documentation-only update. ## Can this PR be safely reverted and rolled back? - [x] YES 💚 This is a documentation change only. Reverting would restore the previous version 2.0 documentation content. --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: ian.alton@airbyte.io <ian.alton@airbyte.io> Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
2.5 KiB
products
| products |
|---|
| all |
import Tabs from "@theme/Tabs"; import TabItem from "@theme/TabItem";
Telemetry
Airbyte collects telemetry data from the UI and the servers to help improve the product. See Airbyte's privacy policy for more details.
If you'd like to turn off telemetry data collection, follow the directions below.
To disable telemetry for your instance, modify the `values.yaml` file and override the hardcoded telemetry setting using component-specific `env_vars` sections: ```yaml
# Override telemetry for server component
server:
env_vars:
TRACKING_STRATEGY: logging
# Override telemetry for worker component
worker:
env_vars:
TRACKING_STRATEGY: logging
```
To turn off telemetry for your instance, modify your values.yaml file and define the following environment variable:
global:
tracking:
strategy: logging
When opening Airbyte or Airbyte's homepage the first time, you're asked for your consent to telemetry collection depending on the legal requirements of your location.
To change this later, do one of the following.
-
In the navigation bar, click your user name > User settings > Cookie Preferences.
-
On Airbyte's website, click Cookie Preferences in the footer.
You can't change server-side telemetry collection in Airbyte Cloud.
When running PyAirbyte for the first time on a new machine, you'll be informed that anonymous usage data is collected, along with a link to this page for more information.
Anonymous usage tracking ("telemetry") helps us understand how PyAirbyte is being used, including which connectors are working well and which connectors are frequently failing. This helps us to prioritize product improvements.
Airbyte never collects any personally identifiable information (PII) or sensitive data. This includes IP addresses, host names, or any other information that could be used to identify you or your organization.
You can opt-out of anonymous usage reporting by setting the environment variable DO_NOT_TRACK to any value.