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>
5.3 KiB
products
| products |
|---|
| all |
Getting Support
Hold up! Have you looked at our docs yet? We recommend searching the wealth of knowledge in our documentation as many times the answer you are looking for is there!
Core support
If you're running Airbyte Core and have a question the docs couldn't clear up, post your question as a Github Discussions and also join our community Slack to connect with other Airbyte users.
Community Slack
Join our Slack community HERE!
Ask your questions first in the #ask-ai channel and if our bot can not assist you, reach out to our community in the #ask-community-for-troubleshooting channel.
If you require personalized support, reach out to our sales team to inquire about Airbyte Enterprise.
Airbyte Forum
We are driving our community support from our forum on GitHub.
Cloud support (Standard, Pro, Enterprise Flex)
If you have questions about connector setup, error resolution, or want to report a bug, Airbyte Support is available to assist you. We recommend checking our documentation and searching our Help Center before opening a support ticket.
If you couldn't find the information you need in our docs or Help Center, open a ticket within the Airbyte Cloud platform by selecting the "Support" icon in the lower left navigation bar. Alternatively, you can submit a ticket through our Help Center by completing an Airbyte Cloud Support Request. Our team is online and availible to assist from 7AM - 7PM Eastern.
If you're unsure about the supported connectors, refer to our Connector Support Levels & Connector Catalog.
For account or credit-related inquiries, contact our sales team.
If you don't see a connector you need, you can submit a connector request.
To stay updated on Airbyte's future plans, take a look at our roadmap.
Please be sure to sign up for Airbyte with your company email address, as we do not support personal accounts.
Self-Managed Enterprise support
If you're running Self-Managed Enterprise, Airbyte's support team here to help you with upgrading Airbyte versions, debugging connector issues, or troubleshooting schema changes.
Before opening a support ticket, we recommend consulting our documentation and searching our Help Center. If your question remains unanswered, please submit a ticket through our Help Center. We suggest creating an Airbyte Help Center account to access your organization's support requests. Our team is online and availible to assist from 7AM - 7PM Eastern.
Connector support is based on certification status of the connector. Please see our Connector Support Levels if you have any questions on support provided for one of your connectors.
Submitting a Pull Request for review?
- Be sure to follow our contribution guidelines laid out here on our doc. Highlights include:
- PRs should be limited to a single change-set
- Submit the PR as a PR Request through the Help Center Open Source Enterprise Support Request form
- If you are submitting a Platform PR we accept Platform PRs in the areas below:
- Helm
- Environment variable configurations
- Bug Fixes
- Security version bumps
- If outside these areas, please open up an issue to help the team understand the need and if we are able to consider a PR
Submitting a PR does not guarantee its merge. The Airbyte support team will conduct an initial review, and if the PR aligns with Airbyte's roadmap, it will be prioritized based on team capacities and priorities.
Although we strive to offer our utmost assistance, there are certain requests that we are unable to support. Currently, we do not provide assistance for these particular items:
- Question/troubleshooting assistance with forked versions of Airbyte
- Configuring using Octavia CLI
- Creating and configuring custom transformation using dbt
- Curating unique documentation and training materials
- Configuring Airbyte to meet security requirements
If you think you will need assistance when upgrading, we recommend upgrading during our support hours, Monday-Friday 7AM - 7PM ET so we can assist if support is needed. If you upgrade outside of support hours, please submit a ticket and we will assist when we are back online.