You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipes are currently executed before tables and stages, which can lead to errors related to tables or stages not existing if they are being created alongside the pipes. A simple fix for this would be moving the pipe registration here to after the snowflake table resource, however this does bring up a larger issue of resource execution order. If each resource were to declare its dependencies, and those we're mapped to create the resources returned by getResources, I feel like that would be a better long term solution. Thoughts?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Pipes are currently executed before tables and stages, which can lead to errors related to tables or stages not existing if they are being created alongside the pipes. A simple fix for this would be moving the pipe registration here to after the snowflake table resource, however this does bring up a larger issue of resource execution order. If each resource were to declare its dependencies, and those we're mapped to create the resources returned by getResources, I feel like that would be a better long term solution. Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions