Legacy Resources I notice that since dagster 1.3,...
# ask-community
Legacy Resources I notice that since dagster 1.3, use of
is now considered legacy. I have put considerable effort into creating a number of resources (which do great and amazing things) and I'm now fearful that I will need to migrate them over to the "new order". In general, I use jobs and ops to construct my workloads (because the software defined assets model doesn't map to my use case as well). How long will legacy resources be available in dagster? Some references: • https://docs.dagster.io/concepts/resourceshttps://docs.dagster.io/concepts/resources-legacyhttps://docs.dagster.io/guides/dagster/migrating-to-pythonic-resources-and-config
🤖 1
Existing resources and config APIs will continue to be supported for the foreseeable future.
👍 1