Bump permissions client to v4, to pull in logging changes #4373
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
bryophyta
force-pushed
the
pf/bump-permissions-client-v4
branch
from
98b27f2 to
441c34d
Compare
Also bump jackson override to match the version in the new permissions client.
bryophyta
force-pushed
the
pf/bump-permissions-client-v4
branch
from
441c34d to
2e18287
Compare
…ested by logstash-logback-encoder I'm not entirely sure why this wasn't a problem before, but logstash-logback-encoder only declares an optional dependency on logback-classic; apps must declare their own dependency on it, but must also be careful to use a version that is compatible. For logstash-logback-encoder 7.4, this is logback-classic 1.3.7 https://github.com/logfellow/logstash-logback-encoder/tree/logstash-logback-encoder-7.4?tab=readme-ov-file#including-it-in-your-project
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.
What does this change?
Bumps the permissions client in order to pull in updates to the logging of casual users' access.
How should a reviewer test this change?
How can success be measured?
Who should look at this?
Tested? Documented?