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
The default config is always used (i.e. the log statement prints out "default_Value" instead of "default_value42"
What did you expect to happen?
The config that is specified in the frontend should overwrite the default config specified in the code.
How to reproduce?
See my example above.
Dagster version
1.9.5
Deployment type
Local
Deployment details
Local & AWS ECS Cluster
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
By submitting this issue, you agree to follow Dagster's Code of Conduct.
The text was updated successfully, but these errors were encountered:
I'm curious as to what the Dagster team has to say about expected behavior of specifying config to the graph, but I can at least give you overrideable-default behavior with this alternative:
My suspicion is that passing a config to a graph, where that config defines op behavior within the graph, sort of "bakes it in"to the graph instance and this might actually be intentional.
What's the issue?
I have this setup of a configured graph
When running it from the frontend with a custom configuration
The default config is always used (i.e. the log statement prints out "default_Value" instead of "default_value42"
What did you expect to happen?
The config that is specified in the frontend should overwrite the default config specified in the code.
How to reproduce?
See my example above.
Dagster version
1.9.5
Deployment type
Local
Deployment details
Local & AWS ECS Cluster
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
By submitting this issue, you agree to follow Dagster's Code of Conduct.
The text was updated successfully, but these errors were encountered: