MySQL-backed event log storage.
Users should not directly instantiate this class; it is instantiated by internal machinery when
dagster-webserver and dagster-graphql load, based on the values in the dagster.yaml file in
$DAGSTER_HOME. Configuration of this class should be done by setting values in that file.
event_log_storage:
 module: dagster_mysql.event_log
 class: MySQLEventLogStorage
 config:
  mysql_db:
   username: { username }
   password: { password }
   hostname: { hostname }
   db_name: { db_name }
   port: { port }
Note that the fields in this config are StringSource and
IntSource and can be configured from environment variables.
MySQL-backed run storage.
Users should not directly instantiate this class; it is instantiated by internal machinery when
dagster-webserver and dagster-graphql load, based on the values in the dagster.yaml file in
$DAGSTER_HOME. Configuration of this class should be done by setting values in that file.
run_storage:
 module: dagster_mysql.run_storage
 class: MySQLRunStorage
 config:
  mysql_db:
   username: { username }
   password: { password }
   hostname: { hostname }
   db_name: { database }
   port: { port }
Note that the fields in this config are StringSource and
IntSource and can be configured from environment variables.
MySQL-backed run storage.
Users should not directly instantiate this class; it is instantiated by internal machinery when
dagster-webserver and dagster-graphql load, based on the values in the dagster.yaml file in
$DAGSTER_HOME. Configuration of this class should be done by setting values in that file.
schedule_storage:
 module: dagster_mysql.schedule_storage
 class: MySQLScheduleStorage
 config:
  mysql_db:
   username: { username }
   password: { password }
   hostname: { hostname }
   db_name: { db_name }
   port: { port }
Note that the fields in this config are StringSource and
IntSource and can be configured from environment variables.