Edge PP issues

[wezell]

Problem Statement

Working with Marc on identifying PP issues that are preventing him from importing a bundle.

• Folder on a non-pushed host gets dragged along in the dependency tree

Failed to Publish Failed to publish because an error occurred: An error occurred when processing Folder in '/data/shared/assets/bundles/01J9Y3ERJFZ37E3GY8SBYJ7E2N/ROOT/1753550752892eb018ce8cee7ecc2178.folder.xml': You can only create an identifier on a host of folder. Trying: null

• Container with live!=working inode

fails to publish because it seems we are only pushing the live inode/version but we try to write the container_version_info from the sender, which references a working inode that might not exist on the receiver.

• Content on a non-pushed host get dragged along and fails to publish

Failed to publish because an error occurred: An error occurred when processing Contentlet: You can only create an identifier on a host of folder. Trying: null

Steps to Reproduce

Ask me for the broken bundle.

Acceptance Criteria

the bundle should import without issue.

dotCMS Version

latest

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[github-actions]

PRs:

• fix(pp) fixing edge push cases where content and folders from non-pushed hosts gets dragged along by dependency, and containers in a drafted state fail to publish #30380

[wezell]

This change introduces a minor breaking change in that it disables the antique /DotAjaxDirector/com.dotcms.publisher.ajax.RemotePublishAjaxAction/cmd/uploadBundle endpoint and suggests to use the /api/bundle/sync endpoint to upload a bundle.

The old endpoint can be reactivated if needed by setting the variable DOT_ENABLE_OLD_BUNDLE_UPLOAD_ENDPOINT = to true