I found some

Question

I found some <https dagster slack com archives CCCR6P2UR p1564084685039000|old conversation> somewhat related but couldn t find anything conclusive Even if a solid inputs is marked optional my execution fails unless I at least configure an empty input with that name Is this expected behavior

alex · Answer

gt Is this expected behavior Yep all inputs must be explicitly satisfied gt Even if a solid inputs is marked optional Can you clarify what you mean here Just want to make sure I m on the same page

alex · Answer

actually came up at the same time in another thread and we believe the reasons we didnt support it from the get go may have changed <https github com dagster io dagster issues 2316>

Will Brown · Answer

My solid function signature has a parameter ` filters Optional str = None ` If I don t supply this argument in my environment dict even if its None then the pipeline says it s missing The dagit yaml editor also highlights the solid element as missing configuration until I put something for all the optional arguments

alex · Answer

thumbsup aligns with the issue above we dont currently support default values on inputs but will likely in the near future