What's new: archiving resources & a new look for deployments
2 min read
Let's take a look at some of the latest features in Faraday.
Archiving resources
We’ve found that Faraday users love to experiment — implementing pipelines in Faraday to predict all kinds of behaviors in different ways. An unfortunate side effect of this is that your Dashboard can get pretty cluttered. Of course, you could always delete your resources, but what if you actually want them back someday?
For this reason, we’ve added the ability for you to archive resources you’ve created in Faraday.
To archive a resource in the Dashboard, simply click the … button on the resource, and click archive. If the resource you’re archiving has downstream dependencies–like an outcome that uses a cohort you’re trying to archive—those will be archived as well. Resources that you've archived can be found using the archived filter in the list view of that resource type. To unarchive a resource, click the unarchive button in the same menu.
For API users, each resource has a POST request specifically for archiving and unarchiving, e.g. archive cohort.
Deployments: new look & the ability to rename
We’ve given the Dashboard's pipeline deployment card a facelift so that it’s easier to tell, at-a-glance, what any given deployment’s purpose is–and added the ability to rename them, too.
The new deployment card now only displays the most critical info by default: connection you’re deploying to, representation format (hashed, identified, etc), and any filters you’ve added (e.g. top 20%). Additional info can be found inside "more details."
By default, a new deployment’s name will be assigned as “Deploy to [connection_name],” but you can now rename them via the ... menu in the upper right of the deployment card. Additionally, you’ll find an indicator for when preview mode is enabled in a deployment card.
For API users, deployments (targets) can be renamed via the PATCH request update a target's name option.
Check out our changelog for a dated list of updates.