this too right?
im a bit worried about this - just a lot of pain to be had if we somehow mess up someones instance config accidentally. If we do like this approach we should put it under more extensive testing.
its also a bit odd that we are storing it there but
not necessarily in this diff but it might be better to move to a scheme where only user edited
telemetry: enabled: True/False
is in the dagster.yaml, and all other metadata is in $DAGSTER_HOME/telemetry next to the log file. Could do something cute like $DAGSTER_HOME/telemtry/id/FILENAME_IS_ID
to your queue for the anonymous case
I do think it might be worth having DagsterInstance in charge the fields stored in dagster.yaml and moving the id out before we ship it - we can discuss that in another medium
clean up prints
could even just delete this in the short term
I would just expose telemetry_enabled instead of the settings
explicitly set default value here
as discussed - can clean this up by having
we may want to remove this broad try catch in the near opt-in term since we will completely lose the errors that are occurring