4f97ee2dab
## What <!-- * Describe what the change is solving. Link all GitHub issues related to this change. --> This pull request updates plan names across most of the Documentation so they're consistent with our current plan names. ## How <!-- * Describe how code changes achieve the solution. --> My original plan was to convert free text to MDX variables so we only had to make future updates to names in one place. While broadly successful, there were numerous edge cases that made rolling this out almost impossible. There were too many ways and places you couldn't use variables due to a variety of limitations in Docusaurus and Airbyte's internal MarkDown processor. Explaining how to properly use them made me realize how prohibitively insufficient this was. In the end, I opted to return to using free text for plan names. Scope is now broadly reduced. This PR: - Converts remaining instances of old plan names to new plan names. In most cases, I replaced old plan names with new plan names directly. In some cases, sentences were rewritten to make a bit more sense or be more maintainable in the future. - Removes previously added preprocessor variables from Docusaurus configuration. - Update Vale styles or various artifacts of content based on linter findings. ## Review guide <!-- 1. `x.py` 2. `y.py` --> Spot check updated pages to ensure plan names appear appropriately. It's probably not necessary to check every single instance in detail. For Platform docs, changes only apply to the Next/Cloud version. After merging, I'll regenerate 2.0 docs based on this. 1.8 and before won't be updated. ## User Impact <!-- * What is the end result perceived by the user? * If there are negative side effects, please list them. --> People can see correct plan names in docs content. ## Can this PR be safely reverted and rolled back? <!-- * If unsure, leave it blank. --> - [x] YES 💚 - [ ] NO ❌ --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@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.