Discover this year's submissions to the Dataiku Frontrunner Awards and give kudos to your favorite use cases and success stories!READ MORE

Warnings on plugins missing in the Automation node

We have lots of plugins on our Designer instance since we are testing them to see if we can use them in our projects. However this means that whenever we deploy a project to the Automation node we get warnings on deployment as the plugin list in the Automation node does not match with the Designer node. This is a bad user experience. Ideally Dataiku should be able to figure out which plugins are used in each project and don't throw Warnings for plugins that are missing in the Automation node but actually are not used in the project being deployed. Dataiku is already able to determine which connections and code environments are used in a project and validate these exist in the destination Automation node being deployed to so the same should be done for Plugins. 

3 Comments
fsergot
Dataiker
Dataiker
Status changed to: In Backlog

Good day,

We have recorded this in the product backlog. We will let you know any progress.

As a side note, having a 100% certainty on which plugins are actually used is not trivial at all, and we don't want to give a false sense of confidence.

tanguy
Level 3

allow me to illustrate this annoying alert 😇

screenshot-warnings.jpg

 

Turribeach
Level 6

"As a side note, having a 100% certainty on which plugins are actually used is not trivial at all, and we don't want to give a false sense of confidence." => Understood but this is not by design, so it can easily be changed. For instance Dataiku could require developers to enable plugins in the Project Settings before being able to use them, which would create a clear way to determine which plugins are "enabled" in each project. Dataiku could also maintain a registry of recipe plugins per project, so this wouldn't need to hard to find out.