DOCS-1808 - Cross-link 1Password app, C2C source, and Automation Service integration - #7066
DOCS-1808 - Cross-link 1Password app, C2C source, and Automation Service integration#7066amee-sumo wants to merge 9 commits into
Conversation
…ice integration Adds recommendation callouts so readers of any one of the three 1Password docs (app, C2C source, Automation Service integration) discover the other two.
…ional callouts Separates the Automation Service integration recommendation from the required setup steps in each doc, so it reads as a supplementary option rather than part of the mandatory flow. Extends the same pattern to AWS Lambda.
Completes the bidirectional link pattern already in place for 1Password.
…on Service integration trios
Applies the same recommendation-callout pattern used for 1Password/AWS Lambda across every additional integration that has 2+ of {C2C source, app, Automation Service integration}: full three-way links where all three exist, and two-way links where only a C2C source + Automation Service integration exist (no app in the docs site).
…ceIntegrationsViaSumoPublicDocumentation
…el471-threat-intel-source)
…urces section Moves the Automation Service Integration callout out of inline :::info blocks and into a consistent "## Additional resources" section at the end of each of the three 1Password docs (app, C2C source, automation integration), and switches the mid-document app/source callouts to :::tip.
kimsauce
left a comment
kimsauce
left a comment
There was a problem hiding this comment.
Reviewed remotely (no local checkout). Verified every added link across all 101 files resolves to the correct file/id (including a couple where the frontmatter id diverges from the filename, e.g. intel-471-threat-intel-source.md → id: intel471-threat-intel-source) — all correct. Two things worth reconciling before merge, both isolated to the 1Password trio; everything else in the PR is consistent. Nice catch fixing the pre-existing "Box" → "Mimecast" copy-paste typo along the way.
| <CollectionConfiguration/> | ||
|
|
||
| :::important | ||
| :::tip |
There was a problem hiding this comment.
This swaps a pre-existing :::important callout to :::tip — that changes the rendered color/icon and doesn't relate to the cross-linking goal of this PR. Was this intentional, or a stray edit? If intentional, worth a separate PR/commit so it's not buried in a cross-linking change.
|
|
||
| <AppUninstall/> | ||
|
|
||
| ## Additional resources |
There was a problem hiding this comment.
Every other app doc in this PR (all ~20 in saas-cloud/, security-threat-detection/, etc.) gets a bare :::info ... ::: block appended, not a ## Additional resources heading. This is the only app doc using the heading pattern, which makes it inconsistent with its own siblings in this same PR. Recommend matching the :::info pattern used everywhere else, unless there's a reason 1Password should stand out here.
| :::info | ||
| After configuring the 1Password source, consider installing the Sumo Logic app for [1Password](/docs/integrations/saas-cloud/1password/) to visualize and analyze the collected data using prebuilt dashboards and monitor alerts. | ||
| :::tip | ||
| After configuring the 1Password source, consider installing the Sumo Logic app for [1Password](/docs/integrations/saas-cloud/1password) to visualize and analyze the collected data using prebuilt dashboards and monitor alerts. |
There was a problem hiding this comment.
Two unrelated changes bundled into this line: the callout type changes from :::info to :::tip, and the [1Password](...) link loses its trailing slash (/1password/ → /1password). trailingSlash: true in docusaurus.config.ts and every other link in this diff keeps the slash, so this looks like an accidental side effect rather than an intentional style change.
| Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources. | ||
| ::: | ||
|
|
||
| ## Additional resources |
There was a problem hiding this comment.
Every other C2C source doc in this PR that already had a "consider installing the app" callout (abnormal-security-source.md, airtable-source.md, automox-source.md, etc.) gets the new Automation Service link merged into that existing :::info block as a second bullet. This file instead leaves that block untouched and adds a brand-new ## Additional resources section at the very end. Recommend merging the link into the existing callout above like its siblings, for consistency.
| * **June 18, 2026** (v1.3) - Updated the integration to allow 1Password to identify API calls from the Sumo Logic integration in their logs for easier tracking and troubleshooting. No newline at end of file | ||
| * **June 18, 2026** (v1.3) - Updated the integration to allow 1Password to identify API calls from the Sumo Logic integration in their logs for easier tracking and troubleshooting. | ||
|
|
||
| ## Additional resources |
There was a problem hiding this comment.
Same as the other two 1Password docs — every other file in automation-service/app-central/integrations/ (74 of them) gets a bare :::info ... ::: block, not a ## Additional resources heading. Worth matching the established pattern for consistency within the PR.
|
|
||
| :::info | ||
| After configuring the Box source, consider installing the Sumo Logic app for [Mimecast](/docs/integrations/saas-cloud/mimecast/) to visualize and analyze the collected data using prebuilt dashboards and monitor alerts. | ||
| After configuring the Mimecast source, consider: |
There was a problem hiding this comment.
Nice incidental fix — this corrects a pre-existing copy-paste typo ("Box source" → "Mimecast source") while adding the new bullet. Just flagging it so it's not mistaken for an unrelated change and accidentally reverted.
2 participants
Purpose of this pull request
This pull request adds recommendation callouts across the 1Password app, Cloud-to-Cloud source, and Automation Service integration docs, so a reader of any one of the three discovers the other two.
(Recreated from #7065, which was inadvertently closed when its head branch was renamed to
staging/DOCS-1808— GitHub deletes the old branch ref as part of a rename, which auto-closes any PR pointing to it. Same commits, same content. Originally #7024 before an earlier rename.)Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1808