How do I run the report_instances commands from the shell?
Table of Contents
This file documents the report_instances resource at the shell, one section per command. Every command is a subcommand of report_instances, and every section exports its own script into projects/ores.shell/scripts/library/. Loading a script runs that one command, so a failure names the command it came from.
1. Commands
1.1. list
Reads one page of the collection. Nothing addresses it but the caller's tenant, so it is the read that shows what exists.
The command is shaped like this:
report_instances list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at reporting.v1.report_instances.list.
report_instances list --limit 1
1.2. get
Reads the one row its key addresses. A key states every identifying column, so a partial key is refused rather than answered with an arbitrary row.
The command is shaped like this:
report_instances get <name>
It is addressed at reporting.v1.report_instances.get.
report_instances get __none__
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
report_instances get-many <name>
It is addressed at reporting.v1.report_instances.get_many.
report_instances get-many __none__
1.4. add
Writes a row. The change states that the row must not exist, so a create that collides with an existing row is refused rather than replacing it. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.
The command is shaped like this:
report_instances add <name> <description> <definition_id> <kind> <run_grant_id> <fsm_state_id> <trigger_id> <output_message> <output_storage_key> <priced_at> <price_note> <engine_settings_id> <engine_settings_version> <cut_id> <cut_label> <cut_kind_code> <cut_timepoint> <reason> <commentary>
It is addressed at reporting.v1.report_instances.put.
report_instances add __none__ __none__ 00000000-0000-0000-0000-000000000000 __none__ - - 00000000-0000-0000-0000-000000000000 __none__ __none__ - __none__ - - - - - - system.new_record generated_script
1.5. set
Writes a row. The change states no precondition, so it replaces whatever row the key already addresses. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.
The command is shaped like this:
report_instances set <id> <name> <description> <definition_id> <kind> <run_grant_id> <fsm_state_id> <trigger_id> <output_message> <output_storage_key> <priced_at> <price_note> <engine_settings_id> <engine_settings_version> <cut_id> <cut_label> <cut_kind_code> <cut_timepoint> <reason> <commentary> [--version <n>]
It is addressed at reporting.v1.report_instances.put.
report_instances set 00000000-0000-0000-0000-000000000000 __none__ __none__ 00000000-0000-0000-0000-000000000000 __none__ - - 00000000-0000-0000-0000-000000000000 __none__ __none__ - __none__ - - - - - - system.new_record generated_script
1.6. put-many
Writes several rows in one request. The count states how many field groups follow. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.
The command is shaped like this:
report_instances put-many --count <n> <id> <name> <description> <definition_id> <kind> <run_grant_id> <fsm_state_id> <trigger_id> <output_message> <output_storage_key> <priced_at> <price_note> <engine_settings_id> <engine_settings_version> <cut_id> <cut_label> <cut_kind_code> <cut_timepoint> <reason> <commentary>
It is addressed at reporting.v1.report_instances.put_many.
report_instances put-many --count 1 00000000-0000-0000-0000-000000000000 __none__ __none__ 00000000-0000-0000-0000-000000000000 __none__ - - 00000000-0000-0000-0000-000000000000 __none__ __none__ - __none__ - - - - - - system.new_record generated_script
1.7. delete
Removes a row. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.
The command is shaped like this:
report_instances delete <name> <reason> <commentary> [--version <n>]
It is addressed at reporting.v1.report_instances.delete.
report_instances delete __none__ system.new_record generated_script
1.8. delete-many
Removes several rows in one request. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.
The command is shaped like this:
report_instances delete-many <name> <reason> <commentary>
It is addressed at reporting.v1.report_instances.delete_many.
report_instances delete-many __none__ system.new_record generated_script
1.9. versions
Reads the row's recorded history, newest first.
The command is shaped like this:
report_instances versions <name> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at reporting.v1.report_instances_versions.list.
report_instances versions __none__ --limit 1
1.10. version
Reads one recorded version of the row.
The command is shaped like this:
report_instances version <name> --version <n>
It is addressed at reporting.v1.report_instances_versions.get.
report_instances version __none__ --version 1