New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge 3.16.1 #1400
Merged
Merged
Merge 3.16.1 #1400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Before this fix, searchLatest filtered the last event of each object (Dictionary or Api) against a list of criteria. Now, searchLatest finds the latest event that matches the criteria, for each object (Dictionary or Api)
Since the searchLatest method has been modified, the sync process for API and dictionaries has to be updated
Using the `canReadAPI` in `AbstractResource` is not sufficient to guarantee that access control is properly enforced. The revision adds a `canManageAPI` method to circumvent CVE83 in an isolated manner and avoid side effects. We should check other usages of `canReadAPI` and ensure that access control meets our expectations. see gravitee-io/issues#6650
Access to API list and access to a single entity were not subject to same permission enforcement, leading to out of sync results between the two resources. see gravitee-io/issues#6475
…elected Adding path mapping works even if the isWithPolicyPaths option is not true
…hMappings feature
elasticsearch kafka connector
since #6847, the gateway loads all latest events of all APIs, even if they are usesless (like UNPUBLISH_API). It implies a very high start time. By adding a search mode (strict or not), the gateway can find the latest event of an API in an efficient way and in the same time benefits from the fix of 6847 for dictionaries events. gravitee-io/issues#6955
When adding new fields in objects that are sent through the http bridge, serialization issue can occurs if http bridge client and server are not in the same version. (for example while upgrading the version of gravitee). These options are added in the mapper used by the http bridge to avoid these issues. gravitee-io/issues#6884
…ate release script
… of plugins in pom.xml
phiz71
approved these changes
Mar 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
gravitee-io/issues#7268
📚 View the storybook of this branch here
🚀 CI was able to deploy the build of this PR, so you can now try it directly here
Notes: The deployed app is linked to the management API of APIM master. (Same login and password as APIM master)