+bengotow

up

up

up

up

• restored correct version of file

In D7419#196106, @alangenfeld wrote:

i think this is a clear step forward even if its json sample in yaml land dagit

also - looks like we are not including commas between fields for the "expected" section when there is extra config? not sure if thats an easy diff to throw out while you're in this zone

resolve inlines before landing

up

rebasing

Trying installation of dagster-graphql to fix build

This seems like a good workflow improvement! Certainly makes the list easier to scan through and emphasizes that the graphs, etc. also only show the most recent run for the partition.

i think we should update all the config_schema arg docstrings to mention this default behavior, e.g. in @solid, SolidDefinition, @resource, and a lot more - esp composite and io manager will behave differently.

Rebasing

Adding dagster-graphql to tox.ini and setup.py in automation

Moving submit_pipeline_execution tests to the GraphQL python client's test suite

@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

Fixing are_queries_compatible

Added regex check to remove redundant spacing from query strings as well

It might be helpful to get more context from the user, are there cases where they couldn't just pull out the user/password/etc? Looks like it wouldn't be too hard postgresql://[user[:password]@][netloc][:port][/dbname][?param1=value1&...]

More complicated than expected - will have to update the k8s run launchers to take in postgres_connection_string_secret rather than postgres_password_secret

Adding checks for redundant dagster-graphql-client query snapshot calls and refactoring

q mgmt

q mgmt

q mgmt

i think this is a clear step forward even if its json sample in yaml land dagit

Rebasing

Responding to comments - refactoring cli to dagster-graphql-client cli

clarify localhost

This will be a huge approachability and general usability win.

fix fixture import

I think this is good. We might eventually want to fork a process for each evaluation, and then change the timeout based on the min interval? But better to make this change and then think through the ramifications of the other stuff.