[DOCS-14086] Remove site support notice from LaunchDarkly integration docs#2992
Merged
Conversation
Add gov2 to the comma-separated region list in the site-region shortcode block in the LaunchDarkly README. US2-FED is a new Datadog GovCloud data center (IL5). Related: DataDog/documentation#36153 (DOCS-14086) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hestonhoffman
requested review from
davidfeng-datadog
and removed request for
a team
brett0000FF
previously approved these changes
May 5, 2026
Site-support banners should be managed centrally in the documentation repo's params.yaml (unsupported_sites), not inline in integration README files. A corresponding PR in DataDog/documentation will add the unsupported_sites entry. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
temporal-github-worker-1
Bot
dismissed
brett0000FF’s stale review
Review from brett0000FF is dismissed. Related teams and files:
- documentation
- launchdarkly/README.md
brett0000FF
approved these changes
May 13, 2026
hestonhoffman
added a commit
to DataDog/documentation
that referenced
this pull request
May 14, 2026
* [DOCS-14086] Add site-support entries for 9 integrations Move site-support banners from inline integration README blocks to centralized unsupported_sites entries in params.yaml. The docs build system renders the banner automatically via path-segment matching when the integration slug is listed as a key. New unsupported_sites entries (all [gov,gov2]): alibaba-cloud, amazon-compute-optimizer, amazon-xray, confluence, confluent_cloud_integration, gitlab-source-code, launchdarkly, oracle-cloud-infrastructure, pagerduty For confluent-cloud, uses a targeted cascade in integrations/_index.md to set site_support_id: confluent_cloud_integration, avoiding a path-segment collision with the api/v2/confluent-cloud/ API reference. Companion PRs that remove the inline banners from integration READMEs: - DataDog/integrations-internal-core#3218 - DataDog/integrations-extras#2992 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Remove amazon-xray and pagerduty from unsupported_sites These integrations have nuanced warnings (commercial-only for X-Ray, limited support for PagerDuty) that belong in the README source, not in centralized site-support. The inline blocks have been reinstated in integrations-internal-core with gov,gov2 targeting. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hestonhoffman
changed the title
bgoldberg122
approved these changes
May 14, 2026
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
3 participants
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.
Removing the LaunchDarkly site support banner. Adding it in the docs repo instead #36672