Project Native Dataiku Applications

importthepandas

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.

melissa

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

xavsun

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

MickaelH

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

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

xavsun

@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

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

AshleyW

@importpandas


You'll be pleased to hear this idea is in our backlog--being able to have instances 'fetch' the latest version from the Application--is a request we've received from customers--and we are determining the next steps for development. We can't provide a timeline at this point, but be sure to check back for updates!

For everyone else, kudos the original post to signal that you're interested in Dataiku developing and releasing this! Feel free to leave a comment in the discussion about how this capability would help you or your team.

Take care,
Ashley

importthepandas

thank you @AshleyW! This is great news.

kenlacrosse

I am also interested in this. I notice that the last post is from a year and a half ago. Is this feature still on backlog or has there been any progress in the meantime?

MickaelH

Hi,

There are no specific update on the front of upgrading app instances but you can also now add a project "setup section" that bring the UI of the app instances to the project home page (as a "Project setup" button). This is achievable with the "advanced options" on the Application Designer home page that offers to configure a "project setup section".

But in this case your users are directly using the same project.