Repository navigation
[backport-aws-7.1] (backport #21462) [aws] Wrap www.amazon.com:app_id examples in backticks to prevent doc-build autolink failures - #21491
Conversation
…-build autolink failures (#21462) * [aws] Prevent autolinking of www.amazon.com:app_id examples in cloudtrail fields The web_id_federation_data.attributes field description used bare www.amazon.com:app_id and www.amazon.com:user_id as illustrative examples. Markdown renderers autolink these into http://www.amazon.com:app_id, and since app_id/user_id aren't valid port numbers, downstream docs-builder link validation fails when it falls back to treating them as relative paths. Wrap the examples in backticks so they render as inline code instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017HKrxUZosBcTRHMBR6o7Fy * [aws] Fix changelog link to point at the actual PR number Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017HKrxUZosBcTRHMBR6o7Fy --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com> (cherry picked from commit 3c8ac0a) # Conflicts: # packages/aws/changelog.yml # packages/aws/manifest.yml
|
Cherry-pick of 3c8ac0a has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Remove cherry-pick conflict markers and unrelated changelog entries, and release the CloudTrail documentation fix as AWS 7.1.4.\n\nCo-Authored-By: GPT-5.6 Sol <noreply@openai.com>
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
🟢 No issues across the latest commits b260c68.
🤖 AI-Generated Review | Vera Review Bot - v0.4.2 | 📚 Knowledge base: integration-skills
|
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
inspector |
1390.82 | 871.84 | -518.98 (-37.31%) | 💔 |
route53_resolver_logs |
9259.26 | 7142.86 | -2116.4 (-22.86%) | 💔 |
apigateway_logs |
31250 | 14705.88 | -16544.12 (-52.94%) | 💔 |
vpcflow |
7142.86 | 5555.56 | -1587.3 (-22.22%) | 💔 |
cloudfront_logs |
3257.33 | 2469.14 | -788.19 (-24.2%) | 💔 |
cloudwatch_logs |
250000 | 200000 | -50000 (-20%) | 💔 |
config |
5714.29 | 3436.43 | -2277.86 (-39.86%) | 💔 |
To see the full report comment with /test benchmark fullreport
|
✅ All changelog entries have the correct PR link. |
|
✅ Package owners are in sync with |
💚 Build Succeeded
History
cc @theletterf |
|
Changelog sync PR created: #21566 |
|
Package aws - 7.1.4 containing this change is available at https://epr.elastic.co/package/aws/7.1.4/ |
Proposed commit message
The
user_identity.session_context.web_id_federation_data.attributesfield in thecloudtraildata stream describes its value with the illustrative exampleswww.amazon.com:app_idandwww.amazon.com:user_id.When
elastic/integration-docsregeneratesdocs/reference/aws/cloudtrail.mdfrom this description, its Markdown renderer autolinks these bare strings into[www.amazon.com:app_id](http://www.amazon.com:app_id). Sinceapp_id/user_idaren't valid port numbers, the docs-builder link validator can't parse the result as an absolute URL, falls back to treating it as a relative file path, and fails the build.This blocked the automated docs-update PR elastic/integration-docs#1412 and elastic/integration-docs#1416 until a temporary workaround was pushed directly to that PR's branch — a patch that would be overwritten on the next docs regeneration since it wasn't fixed at the source.
WHAT: Wrap the two example strings in backticks in
packages/aws/data_stream/cloudtrail/fields/fields.ymlso they render as inline code instead of being autolinked. Regeneratedpackages/aws/docs/cloudtrail.mdwithelastic-package buildto reflect the change, and bumped the package version (7.1.3 → 7.1.4) with a changelog entry.WHY: Fix the underlying field description at the source so future doc regenerations (in this repo and in
elastic/integration-docs) don't hit the autolink/port-number parsing failure, instead of relying on a downstream workaround.The sibling field
web_id_federation_data.federated_provideruses a single barewww.amazon.com(no port-like suffix) and autolinks fine, so it was left unchanged.Checklist
changelog.ymlfile.How to test this PR locally
Run
elastic-package buildinpackages/awsand confirmdocs/cloudtrail.mdregenerates with theweb_id_federation_data.attributesexample values wrapped in backticks.elastic-package lintpasses with only a pre-existing, unrelated warning about thecloudtrailingest pipeline'son_failuremessage.Related issues
🤖 Generated with Claude Code
https://claude.ai/code/session_017HKrxUZosBcTRHMBR6o7Fy
Generated by Claude Code
This is an automatic backport of pull request #21462 done by Mergify.