up

good idea. added a reference to using a secret manager like Vault

+johann

up

We should add template tests to ensure that two services are created when .Values.dagit.enableReadOnly is turned on

Abandoned in favor of D7981

rebase

landable, but note validate tags in an issue if you choose not to resolve it here

rebase

up

rebase

@yuhan The call site would be in the monitoring daemon. Initially this was for the prototype, which is why ALERT_FAILURE was not included, but will do so now.

couple of nits, looks great overall!

up

following along and looks good, but will defer to johann for final signoff

might have to go to the drawing board to decouple partition sets from schedules... (i.e. how can we make partition sets that are not explicitly tied to one of our built in schedules?)

up

just one comment

The API docs for https://dagster-git-sid-python-client-elementl.vercel.app/master/_apidocs/libraries/dagster-graphql#dagster_graphql.DagsterGraphQLClient.reload_repository_location look like they need formatting, but everything else looks great

oooh did not know about this, neat

minor comments

up

up

rebase

Restructure docs to have same format as other pages (Relevant APIs, Overview, Examples, etc)

same comments from https://dagster.phacility.com/D7561

need to update pydantic models and json schema