You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe 👀
Reports versioning introduced conditional upserting of reports on server start and with the upsert-reports-json. Ie, if a report already exists, it won't be upserted.
This makes developing reports difficult, as devs will likely want to rapidly upsert the same report many times while testing without bumping the version.
To change this, we want to introduce an -o (overwrite) flag on the upsert-reports-json command. This will force overwrite reports even if they exist already.
Note this was the behaviour of the upsert-reports-json command prior to the report versioning PR.
Also we want to add a pathing package to the upsert-reports-json command when a reports.json file path is specified. Currently it will search compatibly with mac OS. We want this to be flexible to linux or other systems wherever OMS may be running.
Also need a separate CLI command for use on tester's environment which can access embedded standard reports (not looking through file structure).
This would need to overwrite existing reports in the database.
Describe the solution you'd like 🎁|
Add -o flag to upsert-reports-json command.
Add path package to optional reports json file location.
Separate CLI to upsert bundled standard reports which is usable in tester's environment
Describe alternatives you've considered 💭
Additional context 💌
Moneyworks Jobcode 🧰
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe 👀
Reports versioning introduced conditional upserting of reports on server start and with the
upsert-reports-json
. Ie, if a report already exists, it won't be upserted.This makes developing reports difficult, as devs will likely want to rapidly upsert the same report many times while testing without bumping the version.
To change this, we want to introduce an -o (overwrite) flag on the
upsert-reports-json
command. This will force overwrite reports even if they exist already.Note this was the behaviour of the
upsert-reports-json
command prior to the report versioning PR.Also we want to add a pathing package to the upsert-reports-json command when a reports.json file path is specified. Currently it will search compatibly with mac OS. We want this to be flexible to linux or other systems wherever OMS may be running.
Also need a separate CLI command for use on tester's environment which can access embedded standard reports (not looking through file structure).
This would need to overwrite existing reports in the database.
Describe the solution you'd like 🎁|
upsert-reports-json
command.Describe alternatives you've considered 💭
Additional context 💌
Moneyworks Jobcode 🧰
The text was updated successfully, but these errors were encountered: