Repository navigation
docs(source-google-search-console): fix changelog date, typos, and document missing config options - #75631
Merged
Conversation
…cument missing config options Co-Authored-By: bot_apk <apk@cognition.ai>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| 10. (Optional) For **Data Freshness**, you may choose whether to include "fresh" data that has not been finalized by Google, and may be subject to change. Please note that if you are using Incremental sync mode, we highly recommend leaving this option to its default value of `final`. Refer to the [Data Freshness](#data-freshness) section below for more information on this parameter. | ||
| 11. (Optional) For **Search Analytics API Requests Per Minute**, you may configure the maximum number of requests per minute for Search Analytics API calls. The default value (1200) matches Google's documented maximum quota. If you are experiencing rate limit errors, you may need to lower this value. Most new Google Cloud projects start with a quota of 60 requests per minute. Check your Google Cloud Console quotas to see your actual limit. Refer to the [Rate Limiting](#rate-limiting) section below for more information. | ||
| 12. Click **Set up source** and wait for the tests to complete. | ||
| 11. (Optional) For **Number of Concurrent Workers**, you may configure the number of worker threads used during sync. The default is 40. If you are syncing a large number of site URLs or experiencing rate limit errors, you may want to reduce this value. |
Contributor
There was a problem hiding this comment.
[markdownlint] reported by reviewdog 🐶
MD029/ol-prefix Ordered list item prefix [Expected: 4; Actual: 11; Style: 1/2/3]
Contributor
Author
There was a problem hiding this comment.
The MD029/ol-prefix warnings on lines 11–14 are pre-existing. The numbered list intentionally starts at 8 because items 1–7 are inside a conditional <!-- env:cloud --> block that markdownlint cannot parse. The original file had the same pattern with items 11–12; this PR continues it with items 11–14. No action needed.
| 11. (Optional) For **Search Analytics API Requests Per Minute**, you may configure the maximum number of requests per minute for Search Analytics API calls. The default value (1200) matches Google's documented maximum quota. If you are experiencing rate limit errors, you may need to lower this value. Most new Google Cloud projects start with a quota of 60 requests per minute. Check your Google Cloud Console quotas to see your actual limit. Refer to the [Rate Limiting](#rate-limiting) section below for more information. | ||
| 12. Click **Set up source** and wait for the tests to complete. | ||
| 11. (Optional) For **Number of Concurrent Workers**, you may configure the number of worker threads used during sync. The default is 40. If you are syncing a large number of site URLs or experiencing rate limit errors, you may want to reduce this value. | ||
| 12. (Optional) For **Always Use Aggregation Type Auto**, enable this setting if your search analytics streams fail with a 400 error related to an unsupported `aggregationType`. This overrides the default aggregation type with `auto`, which resolves the error for certain site configurations. |
Contributor
There was a problem hiding this comment.
[markdownlint] reported by reviewdog 🐶
MD029/ol-prefix Ordered list item prefix [Expected: 5; Actual: 12; Style: 1/2/3]
| 12. Click **Set up source** and wait for the tests to complete. | ||
| 11. (Optional) For **Number of Concurrent Workers**, you may configure the number of worker threads used during sync. The default is 40. If you are syncing a large number of site URLs or experiencing rate limit errors, you may want to reduce this value. | ||
| 12. (Optional) For **Always Use Aggregation Type Auto**, enable this setting if your search analytics streams fail with a 400 error related to an unsupported `aggregationType`. This overrides the default aggregation type with `auto`, which resolves the error for certain site configurations. | ||
| 13. (Optional) For **Search Analytics API Requests Per Minute**, you may configure the maximum number of requests per minute for Search Analytics API calls. The default value of 1200 matches Google's documented maximum quota. If you are experiencing rate limit errors, you may need to lower this value. Most new Google Cloud projects start with a quota of 60 requests per minute. Check your Google Cloud Console quotas to see your actual limit. Refer to the [Rate Limiting](#rate-limiting) section below for more information. |
Contributor
There was a problem hiding this comment.
[markdownlint] reported by reviewdog 🐶
MD029/ol-prefix Ordered list item prefix [Expected: 6; Actual: 13; Style: 1/2/3]
| 11. (Optional) For **Number of Concurrent Workers**, you may configure the number of worker threads used during sync. The default is 40. If you are syncing a large number of site URLs or experiencing rate limit errors, you may want to reduce this value. | ||
| 12. (Optional) For **Always Use Aggregation Type Auto**, enable this setting if your search analytics streams fail with a 400 error related to an unsupported `aggregationType`. This overrides the default aggregation type with `auto`, which resolves the error for certain site configurations. | ||
| 13. (Optional) For **Search Analytics API Requests Per Minute**, you may configure the maximum number of requests per minute for Search Analytics API calls. The default value of 1200 matches Google's documented maximum quota. If you are experiencing rate limit errors, you may need to lower this value. Most new Google Cloud projects start with a quota of 60 requests per minute. Check your Google Cloud Console quotas to see your actual limit. Refer to the [Rate Limiting](#rate-limiting) section below for more information. | ||
| 14. Click **Set up source** and wait for the tests to complete. |
Contributor
There was a problem hiding this comment.
[markdownlint] reported by reviewdog 🐶
MD029/ol-prefix Ordered list item prefix [Expected: 7; Actual: 14; Style: 1/2/3]
devin-ai-integration
Bot
added
area/documentation
Contributor
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit 3e4936b. |
dilanalex
pushed a commit
to dilanalex/airbyte
that referenced
this pull request
Apr 6, 2026
…cument missing config options (airbytehq#75631) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: bot_apk <apk@cognition.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation Confidence Assessment
Overall Confidence: 4/5
What I Verified vs. What I Inferred
num_workersconfig option (order 7, default 40, range 2–100) andalways_use_aggregation_type_autoconfig option (order 8, default false) exist inmanifest.yamland are user-facing but were not documented in the setup steps. The changelog entry for v1.10.27 references PR fix(source-google-search-console): guard numeric fields against complex types (AI-Triage PR) #75426, which was merged on 2026-03-30 (not 2026-03-24). The service account JSON key format usesservice_accountwith an underscore.support.google.com/webmasters/answer/7576553) covers the 16-month retention claim — the original third-party blog link explicitly discussed this topic, while the Google link is the closest official equivalent.Areas of Concern
What
Documentation improvements for the Google Search Console source connector, triggered by the merge of #75426 (v1.10.27). Fixes factual inaccuracies and fills documentation gaps for two undocumented user-facing configuration options.
How
Correctness fixes:
2026-03-24→2026-03-30(matches actual merge date of fix(source-google-search-console): guard numeric fields against complex types (AI-Triage PR) #75426)"type": "service account"→"type": "service_account"(matches actual Google JSON key format)Completeness fixes:
Readability/style fixes:
Name" → "using itsName"developers.google.comlink with specific Google Search Console about pageReview guide
docs/integrations/sources/google-search-console.md— single file changedItems worth verifying:
support.google.com/webmasters/answer/7576553) actually covers the 16-month retention claim. The original link was a third-party blog that explicitly discussed this; the new link is Google's official page on data freshness/availability.manifest.yamlspec.site_urlsas an array).User Impact
Users reading the Google Search Console connector docs will see corrected information and will now find documentation for two previously undocumented configuration options visible in the Airbyte UI.
Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/fc5a3b3b5d464303a7445858da1fe3b1