@Fraser Marlow I mean using the output without re-materializing it.
do I need to access the file using I/O manager or is there a way to access it as a parameter similar to how it can be accessed in a downstream asset?
Thanks for your help.
02/03/2023, 1:04 AM
Hi @Yehuda Ornstein - there's not currently an elegant way of doing this in Dagster, but we've been tracking similar requests here: https://github.com/dagster-io/dagster/issues/10874
If you'd be open to sharing what kind of action your job performs, we're trying to understand these use cases a little better
02/03/2023, 1:14 AM
@sandy thanks for the reply. I saw this issue and upvoted it. our use case is very straights forward; we have an asset that gets access tokens for different hosts. There tokens will be used by various jobs. The token asset only needs to be materialized every 12 hours and the jobs run every 5 minutes. if the jobs can use the assets seamlessly it would be great. otherwise the jobs need to get tokens every time they run (or we'll come up with some caching mechanism; not an elegant dagster solution)