- User Since
- Sep 21 2020, 5:44 PM (29 w, 5 d)
Fri, Apr 16
@johann yeah I might have went about this a goofy way - it's probably more simpler to just expose a new field postgres_db.db_params in the storage config, and then just append the urlencoded values to the generated postgresql connection string
More complicated than expected - will have to update the k8s run launchers to take in postgres_connection_string_secret rather than postgres_password_secret
fix fixture import
Thu, Apr 15
Wed, Apr 14
This script looks better placed in python_modules/automation since it's generating some persisted artifacts (the query snapshots) - it should probably be invoked as dagster-graphql-client.
Tue, Apr 13
Add to graphql documentation as well? there are directive you can use to make the classes and associated methods show up
Fri, Apr 9
Thu, Apr 8
Dropping in favor of inspecting the pipeline run's step_keys_to_execute
god bless alex
Fri, Apr 2
Thu, Apr 1
I think from the introductory line in https://docs.dagster.io/concepts/repositories-workspaces/workspaces#workspaces, it should make sense that workspace lives under dagit.
clarifying comment on why dagit needs a workspace
@johann I'm cautious around putting this under dagster-user-deployments since that would generate a manifest used by the parent chart, using values from the subchart. That's a bit confusing. We already do that with dagster-user-deployments.enabled, which is not good.
Wed, Mar 31
Mon, Mar 29
developing -> contributing
update rabbitmq hostname