Do you know the History of Data Science? READ MORE

Project Native Dataiku Applications

Apologies if there is a workaround for this item ahead of time or if this goes against the spirit of Dataiku applications.

Dataiku applications are a big hit on my team. We can spin up forms easily to parameterize models, automate and scale user actions effectively, and much more. However, the one caveat is that in many of the Dataiku apps we create, we'd love to "keep them as part" of the project. Much like dash or shiny apps, so we can easily deploy them to automation without having to deploy the parent project and create a new instance each time.

Each time we update a Dataiku app and re-deploy a test instance, our end user(s) who is our validation point must go to a new URL. Additionally, managed folders and other assets change paths with each instance since they are essentially new projects, requiring a lot of re-work and misalignment from dev to prod.

If there was an option to keep apps native to a project, we'd be ecstatic! They save a lot of time versus having to create simple forms in flask, dash or bokeh and also don't involve as much config and overhead.

6 Comments
melissa
Dataiker
Dataiker
Status changed to: Acknowledged

Thanks for your idea. Your idea meets the criteria for submission, we'll reach out should we require more information. 

xavsun
Level 1

It will make a lot easier for us to manage projects!! Thanks!

MickaelH
Dataiker
Dataiker

Hi,

About 

Each time we update a Dataiku app and re-deploy a test instance, our end user(s) who is our validation point must go to a new URL. Additionally, managed folders and other assets change paths with each instance since they are essentially new projects, requiring a lot of re-work and misalignment from dev to prod.


you should, if it's not already the case, consider using a "real" instance rather than a "test instance". Test instances will indeed always have a unique key while when you create an instance you can specify the (fixed) project key you want to use. 

This way, when you have an update of the dataiku application you can delete the existing instance and recreate it with the same name/project key.

I hope this will help you solve the issues mentioned above.

Regards,

Mickaël | R&D at Dataiku

importthepandas
Level 3

Thanks @MickaelH! That should help cover off the test instance fun 🙂 

xavsun
Level 1

@MickaelH So every time there is a change/enhancement to the parent project, the ‘real’ instance need to be deleted and re-created with a different link again. That won’t be a good user-experience in changing the web link all the time?

MickaelH
Dataiker
Dataiker

Hi,

If you create an instance with the exact same name and project key as the one you deleted the link will be the same.

Regards,

Mickaël | R&D at Dataiku