Add AWSO 2.x to 3.x migration guide with manual and automation scripts#6884
Add AWSO 2.x to 3.x migration guide with manual and automation scripts#6884Apoorvkudesia-sumologic wants to merge 14 commits into
Conversation
Review feedbackA few items to address before merge:
— via Claude Code |
Review feedback (round 2)A few more items from the latest revision:
— via Claude Code |
Review feedback (round 3)One remaining issue that will confuse users: Duplicate numbered steps in manual doc (lines 154–166) — The "Find the new IAM role ARN" section has overlapping instructions. Steps 3–4 appear twice with slightly different wording, and the numbered list restarts at 3 after the first screenshot: This should be a single sequential list (1→2→3→4→5) with screenshots placed between the relevant steps. The old text from before the screenshots were added (lines 154–157) should be removed since lines 159–168 now cover the same steps with proper screenshots. — via Claude Code |
Retain the parent "Deploy and Use AWS Observability" category and split its content into two version subcategories: v3.0.0 (latest) and v2.15.0. Each contains the full doc set. Add a parent launcher landing page, repoint intra-version links, and add redirects for the moved 2.15.0 URLs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rename the v300/v215 subfolders to the dotted v3.0.0/v2.15.0 form and update all references: slugs, intra-version links, sidebar IDs, redirect targets, parent launcher cards, and the migration guides' links into the version docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Update cross-repo markdown links (release notes, API docs, FAQ, about, fedramp, control-tower) that referenced the pre-restructure paths so they resolve to the v2.15.0 version docs, fixing the production build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Purpose of this pull request
This pull request adds changes for the AWSO 2.x.x to 3.x.x migration steps with manual and automation script docs.
Select the type of change
Ticket (if applicable)