[MGNLRES-279] Move Resources URI2RepositoryMapping to processed-resource module Created: 14/Jul/16  Updated: 29/Mar/22  Resolved: 01/Mar/22

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: 2.4.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Bence Vass Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Team: Nucleus

 Description   

The /resources URI2RepositoryMapping is configured by default. but for the new resourcing, it is not needed anymore at all (the class itself is deprecated).

I suggest to remove the URI2RepositoryMapping bootstrap for the resources workspace, and move the URI2ResourcesRepositoryMapping class to the processed resources app, where it is still needed.

Additionally the security of the URI2ResourcesRepositoryMapping should be improved. Since 5.4 FTL and YAML files are present in the resources workspace, and these should not be exposed to website users over the mapping. I will open another issue for that matter in the processed resources project.

—Update: the above was resolved with MGNLRES-281 and MGNLRES-284.


Generated at Mon Feb 12 06:49:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.