changelog migrate-from-web cli command

docs-builder changelog migrate-from-web [options]
		

One-off migration of already-published release notes into the S3 bundle store. For each product in scope, the command:

1. Fetches the release-notes Markdown that backs the published pages — from raw.githubusercontent.com at the pinned commit recorded in the scope table, not by scraping live site HTML.
2. Parses each ## {version} section (typed ### … subsections become entries; prose is preserved as the bundle description) and maps it to the existing bundle YAML shape that changelog upload cli command publishes. No new schema is introduced.
3. Uploads each release to bundle/{product}/{version}.yaml with create-only semantics (If-None-Match: *): keys that already exist are skipped and never overwritten, so the migration can never clobber bundles produced by the live pipeline.
4. Prints a per-key run report (created / skipped / failed, with the reason and object ETag) suitable for pasting into the tracking issue.

By default the command migrates every product in the checked-in scope table; use --products to narrow a run for tests and pilots.

Behaviour flags:

--dry-run — Do everything except the S3 writes and report what would be created.

--products string[]

Optional: restrict the run to specific product ids (comma-separated or repeated), e.g. "edot-java". Defaults to every product in the checked-in scope table.

Repeatable: pass --products multiple times to supply more than one value

--s3-bucket-name string

Destination S3 bucket. Required unless --dry-run; when provided with --dry-run, existing keys are still inspected so the report distinguishes would-create from skipped.

--versions string[]

Optional: restrict the run to specific versions (comma-separated or repeated). Versions above a product's cutoff are always skipped.

Repeatable: pass --versions multiple times to supply more than one value

--[no-]dry-run

Do everything except the S3 writes and report what would be created. (preview changes without applying them)

Default: false

-l --log-level enum

Minimum log level.

Values: trace, debug, information, warning, error, critical, none

Default: information

-c --config-source enum

Override the configuration source: local, remote

Values: local, remote, embedded

--[no-]skip-private-repositories

Skip cloning private repositories

-l --log-level enum

Minimum log level.

Values: trace, debug, information, warning, error, critical, none

Default: information

-c --config-source enum

Override the configuration source: local, remote

Values: local, remote, embedded

--[no-]skip-private-repositories

Skip cloning private repositories

The scope table is checked into the command itself (MigrateFromWebScope.All in the docs-builder repository) rather than into a config file — it is temporary tooling state, added per rollout wave and deleted with the command. Each entry maps a product id (the bundle/{product}/ S3 prefix, see config/products.yml) to the source of its published release notes and a version cutoff:

The page→product mapping is deliberately explicit: bundle product ids appear in no published metadata (page frontmatter carries the site taxonomy, not bundle ids), so deriving it automatically is not possible. Adding a product to the migration is a small PR against the table.

Releases above a product's cutoff are always skipped — they are owned by the live changelog pipeline. Use --versions to narrow a run to specific versions below the cutoff.

Uploads use the same AWS SDK credential chain, region, and IAM permissions as changelog upload cli command. No credentials are needed for --dry-run without --s3-bucket-name.

The report lists one line per key with its outcome:

The command writes YAML bundle objects only — never a registry.json. The scrubber Lambda owns the public bundle/{product}/registry.json manifests and the shallow per-tree maps, reconciling them from the S3 events these creates emit (#3738, #3760).

Parse, map, and report what would be created — no S3 access at all:

docs-builder changelog migrate-from-web --dry-run
		

Also checks which keys already exist, so the report distinguishes would-create from skipped:

docs-builder changelog migrate-from-web \
  --dry-run \
  --s3-bucket-name my-changelog-bundles
		

docs-builder changelog migrate-from-web \
  --s3-bucket-name my-changelog-bundles
		

Re-running the same command is safe: every existing key is reported as skipped and the run is a no-op.

docs-builder changelog migrate-from-web \
  --products edot-java \
  --s3-bucket-name my-changelog-bundles
		

docs-builder changelog migrate-from-web \
  --products edot-java \
  --s3-bucket-name my-changelog-bundles \
  --versions 1.9.0,1.10.0