Skip to content
This repository has been archived by the owner on Jun 1, 2024. It is now read-only.

beagle-spring-starter interferes with pre-existing endpoints #1822

Closed
manosbatsis opened this issue Sep 20, 2022 · 2 comments · Fixed by ZupIT/beagle-backend-kotlin#98
Closed
Assignees

Comments

@manosbatsis
Copy link

Use case

Using beagle-spring-starter seems to interfere with existing REST, JSON-API, GraphQL etc. endpoints.

Proposal

Add a configuration property or HOWTO for restricting Beagle's URL matches based on:

  1. URL pattern(s) e.g. /sdui/** and/or
  2. existence of BeaglePlatformUtil.BEAGLE_PLATFORM_HEADER as an HTTP request header
@Tiagoperes
Copy link
Contributor

Thanks for reporting. @hernandazevedozup will check this asap.

@hernandazevedozup
Copy link
Contributor

The fix for this issue has been released on 2.0.2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants