Refactor Organization Resource Resolver to Avoid Cyclic Dependencies

[Yasasr1]

Description

Issue

The current Organization Resource Resolver service provides two key capabilities:

• Retrieving resources by traversing the hierarchy of a given organization and application.
• Retrieving resources by traversing the hierarchy of a given organization.

However, invoking this service within idp-mgt (or any other service that depends on app-mgt) can lead to cyclic dependencies due to its tight coupling with application-specific logic.

Proposed Solution

Extract the application-specific traversal logic into a separate service. This refactor will help:

• Decouple application logic from the core resolver.
• Eliminate potential circular dependencies across services.

Version

IS 7.2

[Yasasr1]

Related prs

• Refactor organization resource resolver service wso2-extensions/identity-organization-management#510
• Update usages of the organization resource resolver service wso2-extensions/identity-event-handler-notification#325
• Update org.wso2.identity.organization.mgt.imp.pkg.version.range wso2-extensions/identity-auth-organization-login#59
• Update org.wso2.identity.organization.mgt.imp.pkg.version.range wso2-extensions/identity-oauth2-grant-organization-switch#40
• Bump org.wso2.identity.organization.mgt.imp.pkg.version.range identity-organization-management-core#178
• Update carbon.identity.organization.management.version.range wso2-extensions/identity-inbound-auth-oauth#2795
• Bump identity.org.mgt.application.version.range identity-apps#8233
• Use correct service range for org-resource-resolver service carbon-identity-framework#6791
• Bump org.wso2.carbon.identity.organization.management.version.range wso2-extensions/identity-carbon-auth-rest#317
• Bump identity.organization.management.imp.pkg.version.range. wso2-extensions/identity-branding-preference-management#54

[Yasasr1]

This task changes the organization resource resolver interface to remove an existing method and introduce a new service. So considering the impact to the developers who use the existing interface, this can be considered as a behavioural change