[CFGUI-32] Fix and streamline configuration source type resolution and presentation in overview sub-app Created: 03/Aug/16  Updated: 09/Feb/17  Resolved: 19/Aug/16

Status: Closed
Project: Definitions App
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Philip Mundt Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to CFGUI-16 Transform 'Show file' button into 'Sh... Closed
dependency
depends upon MAGNOLIA-6081 Consider providing datasource type in... Closed
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
Epic Link: Definitions app
Sprint: Basel 57
Story Points: 3

 Description   

The following issue has to be addressed

  • Definitions that are hot-fixed within resources-app are considered as config-based definitions => show file action broken

This happens due to a mis-understanding of how does the notion of configuration source correlates with ResourceOrigins and with JCR config and resources workspaces. The following logic should be used:

  • Anything that is served via the ResourceOrigin (this includes JCR resources workspace) is treated as a file-based definition
  • Anything that comes from JCR config workspace is treated as a JCR definition.

Luckily to simplify this - MAGNOLIA-6081 brings us a new simple API which allows to ask a DefinitionProvider - which config source it initially is coming from.

As a complement to this effort - we should re-purpose the Source column in the overview table - let it omit the information about the exact origin of the file-based definition (i.e. FS, classpath or resources workspace), they all are in the end are files.


Generated at Mon Feb 12 00:44:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.