With the March update, can artifacts/items metadata be stored directly in OneLake?

[dhrumil83]

With the current architecture, workloads must save and manage artifacts/items metadata on it's own.
https://learn.microsoft.com/en-us/fabric/workload-development-kit/item-lifecycle

Looking at the March update, does this mean that workloads can optionally save item metadata directly in OneLake along with the item name, description, and type?

https://github.com/microsoft/Microsoft-Fabric-workload-development-sample/pull/209/files#diff-7bdc6b6a4c0a4e307905b83efba6b61f919043429f3bb23610bdab9c8b727302R43

[dhrumil83]

This adds the ability to store the result of the sample workload in OneLake(was Lakehouse earlier), but we still need to store metadata about the item itself on our BE.