When viewing a build that reconfigures pipelines, it's hard to tell which pipelines were actually changed:

Quick suggestion: highlight it in yellow, like the get step? Or the opposite - dim steps which had no changes to apply? No strong preference!

This would likely involve emittin

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Problem
Since Java 8 was introduced there is no need to use Joda as it has been replaced the native Date-Time API.

Solution
Ideally greping and replacing the text should work (mostly)

Additional context
Need to check if de/serializing will still work.

Is your feature request related to a problem? Please describe.
SNS endpoint subscriptions must expose a public facing HTTP server ( unless I missed something ) and therefore make it possible for untrusted sources to post messages to the event bus as long as the message comply with basic message format.

Describe the solution you'd like
The SNS source should verify the signature of the

As pointed out in #758 paste button is always enabled, even when setting it to false in toolbarConfig.
Paste events on common canvas should be cleared after clearing a pipeline or when opening an empty pipeline.

Hi!

When using the unprivileged image, it's not possible to load custom configurations.

# podman run -p 8080:8080 -e GITLAB_MONITOR_CONFIG=/tmp/config.json timoschwarzer/gitlab-monitor:unprivileged
/wrapper.sh: line 4: can't create /usr/share/nginx/html/config.json: Permission denied

Indeed, root is needed to create a new file in /usr/share/nginx/html, and it looks like wrapper.s

Expected Behavior

If a user adds a new annotation/label to an EventListener, we should propagate that down to the underlying deployment and service.

One use case:

• Propagating service specific annotations e.g. for LoadBalancer services one might specify load balancer specific annotations

Actual Behavior

We propagate labels but not annotations

Additional Info

• current code: h

Current save/load methods focus on dumping and loading the pipeline definition in its JSON form, but provide no means to save a fitted pipeline and load it later to make predictions, being the usage of pickle outside of the pipeline the only way to go.

Let's re-implement the save/load methods to save the whole pipeline instance, and move the current save functionality to a to_json method.