Hi @little-cricket-84530, I noticed that you've been wanting to use

FlyteDirectory

as an input with Copilot for a while now, and I'm pleased to inform you that it's now supported! (Done by @full-toddler-99513) Recently, @full-toddler-99513 has put a lot of effort into understanding how Copilot works and its constraints. For example, we're planning to support nested

FlyteDirectory

outputs (currently, we support

FlyteDirectory

but not nested ones). Are there any other enhancements you'd like to see in Copilot? We'd be happy to explore adding support for them.

@damp-lion-88352 so when this goes out, using FlyteDirectory as input for ContainerTask is supported? That is huge!

YES

OMG, that release will be massive. Thank you @full-toddler-99513 @damp-lion-88352!

yes please bring him to the contributor spotlight, really deserve it

Fabulous! I'm trying to recall what my original use case was 😬

Thank you for the shoutout, @damp-lion-88352!