All work
- Remove "Okapi Integration" modeMGRAPPS-55
- Provide "System User required" attribute as part of module bootstrap dataMGRAPPS-54
- Enable security by defaultMGRAPPS-52Mykola Makhin
- Release mgr-applications v2.1.0 Ramsons SP#1 Release (R2 2024)MGRAPPS-50Resolved issue: MGRAPPS-50Mykola Makhin
- Extend mgr-applications validateApplicationDescriptor endpoint to support modulesInterfaceIntegrityValidationMGRAPPS-49Aliaksei Harbuz
- Include modulePermissions info in bootstrap API responsesMGRAPPS-48Resolved issue: MGRAPPS-48Craig McNally
- Backport to Ramsons: Include modulePermissions info in bootstrap API responsesMGRAPPS-47Resolved issue: MGRAPPS-47Mykola Makhin
- Update to mgr-applications Java 21MGRAPPS-46Resolved issue: MGRAPPS-46Mykola Makhin
- Not able to entitle applications after routes migration.MGRAPPS-45Resolved issue: MGRAPPS-45Mykola Makhin
- Include permissionSet info in bootstrap API responsesMGRAPPS-44Resolved issue: MGRAPPS-44Mykola Makhin
- Release mgr-applications v2.0.3 Ramsons bugfix Release (R2 2024)MGRAPPS-43Resolved issue: MGRAPPS-43Mykola Makhin
- Release mgr-applications v2.0.2 Ramsons SP#1 Release (R2 2024)MGRAPPS-42Resolved issue: MGRAPPS-42Mykola Makhin
- DELETE discovery endpoint behaves strangelyMGRAPPS-41Resolved issue: MGRAPPS-41Artem Akimov
- Release mgr-applications v1.4.1 Quesnelia R1 2023 SP #9 ReleaseMGRAPPS-39Resolved issue: MGRAPPS-39Pavel Filippov
- mgr-applications - Backport Keycloak 26.x to QuesneliaMGRAPPS-40Resolved issue: MGRAPPS-40Pavel Filippov
- Release mgr-applications v2.0.1 Ramsons SP#1 Release (R2 2024)MGRAPPS-38Resolved issue: MGRAPPS-38Yauhen Vavilkin
- mgr-applications - Upgrade to Keycloak 26.xMGRAPPS-37Resolved issue: MGRAPPS-37Pavel Filippov
- Reduce number of redundant routes in KongMGRAPPS-35Resolved issue: MGRAPPS-35Mykola Makhin
- Release mgr-applications v2.0.0 Ramsons Release (R2 2024)MGRAPPS-33Resolved issue: MGRAPPS-33Yauhen Vavilkin
- Release mgr-applications v1.4.0MGRAPPS-32Resolved issue: MGRAPPS-32Yauhen Vavilkin
- Release mgr-applications v1.3.3MGRAPPS-30Resolved issue: MGRAPPS-30Oleksii Kuzminov
- Revert MGRAPPS-23MGRAPPS-29Resolved issue: MGRAPPS-29Oleksii Kuzminov
- Egress module information is duplicated in module-bootstrapMGRAPPS-28
- Release mgr-applications v1.3.2MGRAPPS-26Resolved issue: MGRAPPS-26Dima Tkachenko
- Add "extensions" field to module descriptorMGRAPPS-23Resolved issue: MGRAPPS-23Pavel Filippov
- Release mgr-applications v1.3.1MGRAPPS-22Resolved issue: MGRAPPS-22Dima Tkachenko
- Release mgr-applications v3.0.0 Sunflower Release (R1 2025)MGRAPPS-51Resolved issue: MGRAPPS-51Dima Tkachenko
- Allow an optional "attributes" property in modules/uiModules' entries in application descriptorsMGRAPPS-21
- Release mgr-applications v1.3.0MGRAPPS-20Resolved issue: MGRAPPS-20Oleksii Kuzminov
- Upgrade to folio-security with keycloak 24MGRAPPS-19Resolved issue: MGRAPPS-19Pavel Filippov
- Support HTTPS in TenantEntitlementClientMGRAPPS-18Resolved issue: MGRAPPS-18Yaroslav Kiriak
- Release mgr-applications v1.2.0MGRAPPS-17Resolved issue: MGRAPPS-17Dima Tkachenko
- Upgrade to spring-core 6.1.3 or laterMGRAPPS-16Resolved issue: MGRAPPS-16
- Upgrade to Guava 32.0.0MGRAPPS-14Resolved issue: MGRAPPS-14
- HTTPS access to KongMGRAPPS-13Resolved issue: MGRAPPS-13Yaroslav Kiriak
- Create a docker file for the mgr-applications module that is based on the FIPS-140-2 compliant base image (ubi9/openjdk-17-runtime)MGRAPPS-12Resolved issue: MGRAPPS-12Dima Tkachenko
- Add `permissionsDesired` to a module bootstrap dataMGRAPPS-11Resolved issue: MGRAPPS-11Yauhen Vavilkin
- Secure mgr-applications HTTP end-points with SSL using FIPS-140-2 compliant crypto modulesMGRAPPS-10Resolved issue: MGRAPPS-10Oleksii Kuzminov
- Release mgr-applications v1.1.0MGRAPPS-9Resolved issue: MGRAPPS-9Pavel Filippov
- Investigate options for removing module name prefixMGRAPPS-8Resolved issue: MGRAPPS-8Pavel Filippov
- Define application descriptors for initial LoC DeploymentMGRAPPS-7Resolved issue: MGRAPPS-7Oleksii Kuzminov
- Release mgr-applications v1.0.0MGRAPPS-6Resolved issue: MGRAPPS-6Oleksii Kuzminov
- Enable API-related GitHub WorkflowsMGRAPPS-4Resolved issue: MGRAPPS-4David Crossley
- [Bug] Nullpointer during the installation of edge modulesMGRAPPS-3Resolved issue: MGRAPPS-3Oleksii Kuzminov
- mgr-applications - self register routes in Kong at startupMGRAPPS-2Resolved issue: MGRAPPS-2Pavel Filippov
- PLACEHOLDER - mgr-applications - Make discovery information work at the module level, not application level.MGRAPPS-1
- CO - Incorporate the flow engineMGRAPPS-5Resolved issue: MGRAPPS-5
- CO - mgr-components - null fields must be excluded from jsonb schemasMGRAPPS-31
48 of 48
Remove "Okapi Integration" mode
Description
Environment
None
Potential Workaround
None
has to be done before
is cloned by
Checklist
hideDetails
Assignee
UnassignedUnassignedReporter
Craig McNallyCraig McNallyLabels
Priority
P3Story Points
2Development Team
EurekaRelease
Umbrellaleaf (R3 2025)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Craig McNally
Craig McNallyLabels
Priority
P3Story Points
2
Development Team
Eureka
Release
Umbrellaleaf (R3 2025)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 28, 2025 at 6:12 PM
Updated March 31, 2025 at 12:30 PM
Activity
Show:
The “Okapi integration” mode, aka “compatibility mode”, mgr-applications makes calls to Okapi. This mode was never fully testing and as it turns out was not really needed. To help with code readability, maintainability, and to avoid confusion, this should be removed, simplifying the code.
Scope:
Remove branching/logic related to OKAPI integration mode
Update application.yaml, README.md, etc.
Update tests as needed.
changes in applications-poc-tools is out of scope. This will be handled in a separate story.