Typically when deploying Lily, a config.toml is created to setup persistence targets for jobs via the --storage arg (which is the only way to configure persistence options on a Job. This is inconsistent with lily migrate which require --db and --schema flags. As a suggested UX improvement, it would good to make lily migrate --storage the default interaction and deprecate the old flags.
Acceptance criteria
Storage options passed in as lily migrate --storage=TARGET instead of lily migrate --db=LONGCONNECTIONSTRING --schema=SCHEMANAME.
Where to begin
Add --storage
Deprecate --db and --schema with notice while still respecting their values
Description
Typically when deploying Lily, a
config.toml
is created to setup persistence targets for jobs via the--storage
arg (which is the only way to configure persistence options on a Job. This is inconsistent withlily migrate
which require--db
and--schema
flags. As a suggested UX improvement, it would good to makelily migrate --storage
the default interaction and deprecate the old flags.Acceptance criteria
lily migrate --storage=TARGET
instead oflily migrate --db=LONGCONNECTIONSTRING --schema=SCHEMANAME
.Where to begin
--storage
--db
and--schema
with notice while still respecting their values