Skip to content

MWPW-196039: Scope bulk publish projects folder per subtenant#965

Open
Axelcureno wants to merge 8 commits into
mainfrom
MWPW-196039
Open

MWPW-196039: Scope bulk publish projects folder per subtenant#965
Axelcureno wants to merge 8 commits into
mainfrom
MWPW-196039

Conversation

@Axelcureno

Copy link
Copy Markdown
Member

Resolves https://jira.corp.adobe.com/browse/MWPW-196039

Moves bulk publish projects from /content/dam/mas/bulk-publish-projects/{surface} to /content/dam/mas/{surface}/bulk-publish-projects so IAM POWERUSERS publish rights can be scoped per surface.

  • BULK_PUBLISH_PARENT_PATHBULK_PUBLISH_PROJECTS_FOLDER; all parentPath construction routed through getBulkPublishParentPath(surface) in mas-repository
  • Per-subtenant folders already created in prod (2026-06-11)
  • Out of scope: migration of existing tenant-root projects (follow-up ticket) and IAM group scoping (ops)

Verified locally: project create returns 201 with the new parentPath; project list queries the new path.

QA Checklist: https://wiki.corp.adobe.com/display/adobedotcom/M@S+Engineering+QA+Use+Cases

  • C1. Cover code with Unit Tests
  • C2. Add a Nala test (double check with #fishbags if nala test is needed)
  • C3. Verify all Checks are green (unit tests, nala tests)
  • C4. PR description contains working Test Page link where the feature can be tested
  • C5: you are ready to do a demo from Test Page in PR
  • C.6 read your Jira one more time to validate that you've addressed all AC's and nothing is missing

Test URLs:

Move bulk publish projects from /content/dam/mas/bulk-publish-projects/{surface}
to /content/dam/mas/{surface}/bulk-publish-projects so IAM POWERUSERS rights can
be scoped per surface (matches existing settings/translations layout).

Replaces BULK_PUBLISH_PARENT_PATH with BULK_PUBLISH_PROJECTS_FOLDER and routes
all parentPath construction through getBulkPublishParentPath() in mas-repository.
# Conflicts:
#	studio/src/bulk-publish/mas-bulk-publish-editor.js
#	studio/src/mas-repository.js
@aem-code-sync

aem-code-sync Bot commented Jun 11, 2026

Copy link
Copy Markdown

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-sync branch
Commits

# Conflicts:
#	studio/src/mas-repository.js
@codecov

codecov Bot commented Jun 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.25%. Comparing base (4770599) to head (ed243c8).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #965      +/-   ##
==========================================
+ Coverage   89.21%   89.25%   +0.03%     
==========================================
  Files         264      264              
  Lines       82885    82889       +4     
==========================================
+ Hits        73945    73979      +34     
+ Misses       8940     8910      -30     
Files with missing lines Coverage Δ
studio/src/bulk-publish/mas-bulk-publish-editor.js 88.80% <100.00%> (-0.02%) ⬇️
studio/src/bulk-publish/mas-bulk-publish.js 93.22% <100.00%> (ø)
studio/src/mas-repository.js 74.29% <100.00%> (+0.05%) ⬆️

... and 6 files with indirect coverage changes


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4770599...ed243c8. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

3 participants