Skip to content

feat(content): admin.hlx.page bulk preview/publish on push#2710

Open
davidnuescheler wants to merge 1 commit intomainfrom
feat/content-push-admin-preview-publish
Open

feat(content): admin.hlx.page bulk preview/publish on push#2710
davidnuescheler wants to merge 1 commit intomainfrom
feat/content-push-admin-preview-publish

Conversation

@davidnuescheler
Copy link
Copy Markdown
Contributor

Summary

Adds --preview and --publish to aem content push so that after a successful da.live sync, the CLI can start bulk preview and/or bulk publish jobs on admin.hlx.page using the same DA/IMS bearer token.

  • --preview: bulk preview for changed paths (add/update and, when needed, delete).
  • --publish: runs bulk preview first, waits for those jobs to finish, then bulk publish.
  • Paths: .html resources are sent extensionless (e.g. /x/page.html/x/page) for preview/publish payloads.
  • Ref: current git branch from the project directory, with ?branch= when the branch name has slashes or uppercase letters.

Testing

  • test/content/hlx-admin.test.js, updates to test/content/push.cmd.test.js and test/content/content-commands.test.js.

Made with Cursor

- Bulk preview (POST /preview/.../*) and bulk publish (POST /live/.../*)
- --publish waits for preview jobs before publish jobs; same DA/IMS token
- Strip .html suffix for admin bulk paths (extensionless web URLs)
- Git branch from project root for ref; branch query for slashes/uppercase
- Tests for hlx-admin helpers and push integration

Made-with: Cursor
@tripodsan
Copy link
Copy Markdown
Contributor

--publish: runs bulk preview first, waits for those jobs to finish, then bulk publish.

are you sure you want to run preview + publish for --publish ?

why not just specify both?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants