the way I've been handling this is to store schedule/sensor parameters that I want to be able to change in AWS Systems Manager Parameter Store, then retrieving them from within the sensor definition. you could really use any external state store (S3, postgres, secrets manager etc.). then you can switch out the parameter values outside of the code. you can even build a dagster job for changing / setting the the values in Systems Manager so you can get a config schema interface and a bit of an audit log of when changes were made to the parameters. it's not ideal but it works