Skip to content

Fixes/coercion error logbook class filtering dynamic update#1430

Open
zan-mateusz wants to merge 3 commits intoapache:masterfrom
zan-mateusz:fixes/coercion-error-logbook-class-filtering-dynamic-update
Open

Fixes/coercion error logbook class filtering dynamic update#1430
zan-mateusz wants to merge 3 commits intoapache:masterfrom
zan-mateusz:fixes/coercion-error-logbook-class-filtering-dynamic-update

Conversation

@zan-mateusz
Copy link
Copy Markdown
Contributor

3 fixes in separate commits:

  1. Type coercion when triggering an effector that contains a JSON list.
    When using a yaml list as input to an effector e.g.:
  • hello
  • world
    Currently it is parsed as a multiline string so you get - and newline chars included. Commit 1 fixes this situation so we now get correctly: "[\"hello\",\"world\"]"
  1. Logbook enhancement to allow filtering based on class/logger name perfix
    Enhancement to allow filtering based on the prefix of logger name. It is accompanied by a minor UI tweak in a separate PR in brooklyn-ui. Current search capability does not allow searching for class names, just the message content, this enhancement allows it.

  2. Fix for cases where a bundle gets updated and an application deployed before update does not use the updated bundle
    Currently, when the user updates a bundle version with an application deployed with previous version, operations on that application do not use the updated bundle UNTIL server is restarted. This PR fixes this behavior by processing update headers correctly during bundle installation. Also the application itself was still pointing at the previous version classpath, so a fix has been introduced to migrate running applications correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant