@smart-cloud/publisher-exporter 1.2.14 → 1.2.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +12 -3
- package/dist/cli.js +1 -1
- package/dist/content-sync.js +16 -16
- package/dist/crawl.js +14 -14
- package/dist/deploy.js +6 -6
- package/dist/invalidate.js +3 -3
- package/dist/queue-runner.js +3 -3
- package/dist/remote-worker-health.js +1 -1
- package/dist/remote-worker.js +6 -6
- package/dist/rewrite-worker.js +2 -2
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -772,8 +772,15 @@ planning local. Admitted pages are grouped into bounded Lambda batches. Their
|
|
|
772
772
|
HTML stays in S3, while each result returns discovered pages/assets and an
|
|
773
773
|
object reference. Asset workers fetch and inspect bounded URL batches. Final text
|
|
774
774
|
objects are rewritten in place by Lambda, then deploy workers check or copy
|
|
775
|
-
them directly from the workspace to the allowlisted target.
|
|
776
|
-
|
|
775
|
+
them directly from the workspace to the allowlisted target. A successful,
|
|
776
|
+
unlimited full crawl rebuilds its desired manifest from current captures and
|
|
777
|
+
current copy sources. After every upload succeeds, `sdk-upload-delete` reconciles
|
|
778
|
+
the complete target prefix against that manifest. The independently managed
|
|
779
|
+
`static/config/foundation/` prefix is preserved. Profile rebuilds also preserve
|
|
780
|
+
Guardian's independently refreshed ordinary `smartcloud-wpsuiteio/lic.jws` and
|
|
781
|
+
`config.enc` root keys. Incremental, URL, resumed,
|
|
782
|
+
page-limited and partial crawls use explicit deploy-plan tombstones instead.
|
|
783
|
+
Each completed
|
|
777
784
|
batch updates phase-scoped runtime progress and adds a structured batch summary
|
|
778
785
|
to `deploy.log.jsonl`; debug logging also records each returned object result.
|
|
779
786
|
There is no silent local fallback for any
|
|
@@ -786,7 +793,9 @@ enabled remote phase.
|
|
|
786
793
|
- If direct CLI execution seems to ignore the expected runtime state, verify that `PUBLISHER_CONFIG` and `STATIC_PUBLISHER_RUNTIME_DIR` both point at the same runtime tree. A mismatched config path and runtime dir can make the run look idle or incomplete.
|
|
787
794
|
- Prefer incremental crawl when the existing manifest is trusted and you only need a fast recrawl of changed pages or assets. Prefer a full crawl when discovery rules changed, the manifest is missing or suspect, or you want a clean end-to-end rebuild.
|
|
788
795
|
- JavaScript bundle discovery follows only explicit dynamic `import()` calls and fixed Webpack chunk-filename mappings such as `runtime.u = () => "custom-block-parser.js"`. It does not infer dependencies from arbitrary quoted paths or application-specific loader calls; add those manually as extra assets when needed.
|
|
789
|
-
-
|
|
796
|
+
- A full rebuild requires an unlimited crawl without resume and without failed pages. It replaces stale manifest state and old copy outputs; unchanged files still present in the current copy source remain desired. Partial and page-limited runs never authorize complete target cleanup.
|
|
797
|
+
- Captured profile license, encrypted configuration and translation payloads retain their exact source bytes. They are refreshed from the source and do not need URL rewriting inside their contents. Translation catalogs follow the current source revision. Connection assets compare the saved source timestamp with the target source timestamp (or S3 `LastModified` for externally refreshed objects), retain a newer target, and use conditional writes to avoid overwriting a concurrent Guardian refresh. The source timestamp comes from Hub's `Last-Modified`, not from the capture time; unknown source time retains an existing connection asset with a diagnostic decision. These decisions are recorded in the deploy log.
|
|
798
|
+
- In `sdk-upload-delete` mode, incremental, URL, resumed, page-limited and partial jobs protect remote-only S3 objects unless their plan contains an explicit deletion tombstone. A successful complete full rebuild removes remote-only objects from its target prefix after successful uploads, preserving the Foundation configuration prefix. `sdk-upload-only` never deletes objects. New full reconciliation and source freshness behavior require the corresponding deploy worker capabilities.
|
|
790
799
|
- `queue-runner-heartbeat.json` reports both the exporter package version and the installed `@smart-cloud/wpsuite-core` version. Crawl logs also report the runtime `virtualAssetBaseUrl`, remote config loader status, and resolved subscription type without logging the runtime token. Legacy runtime input using `uploadUrl` is accepted during migration but normalized to `virtualAssetBaseUrl`.
|
|
791
800
|
- For generated 404 capture, set `generated404RequestPath` to a path that really returns HTTP 404 from the origin. The exporter validates that response before reusing it as the generated 404 page.
|
|
792
801
|
|