How do I run the credit_simulation_configs commands from the shell?
Table of Contents
This file documents the credit_simulation_configs resource at the shell, one section per command. Every command is a subcommand of credit_simulation_configs, 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:
credit_simulation_configs list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.credit_simulation_configs.list.
credit_simulation_configs 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:
credit_simulation_configs get <name>
It is addressed at analytics.v1.credit_simulation_configs.get.
credit_simulation_configs get __none__
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
credit_simulation_configs get-many <name>
It is addressed at analytics.v1.credit_simulation_configs.get_many.
credit_simulation_configs 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:
credit_simulation_configs add <name> <configuration_id> <market> <credit> <zero_market_pnl> <evaluation> <double_default> <seed> <paths> <credit_mode> <loan_exposure_mode> <reason> <commentary>
It is addressed at analytics.v1.credit_simulation_configs.put.
credit_simulation_configs add __none__ 00000000-0000-0000-0000-000000000000 __none__ __none__ false __none__ false 0 0 __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:
credit_simulation_configs set <id> <name> <configuration_id> <market> <credit> <zero_market_pnl> <evaluation> <double_default> <seed> <paths> <credit_mode> <loan_exposure_mode> <reason> <commentary> [--version <n>]
It is addressed at analytics.v1.credit_simulation_configs.put.
credit_simulation_configs set 00000000-0000-0000-0000-000000000000 __none__ 00000000-0000-0000-0000-000000000000 __none__ __none__ false __none__ false 0 0 __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:
credit_simulation_configs put-many --count <n> <id> <name> <configuration_id> <market> <credit> <zero_market_pnl> <evaluation> <double_default> <seed> <paths> <credit_mode> <loan_exposure_mode> <reason> <commentary>
It is addressed at analytics.v1.credit_simulation_configs.put_many.
credit_simulation_configs put-many --count 1 00000000-0000-0000-0000-000000000000 __none__ 00000000-0000-0000-0000-000000000000 __none__ __none__ false __none__ false 0 0 __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:
credit_simulation_configs delete <name> <reason> <commentary> [--version <n>]
It is addressed at analytics.v1.credit_simulation_configs.delete.
credit_simulation_configs 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:
credit_simulation_configs delete-many <name> <reason> <commentary>
It is addressed at analytics.v1.credit_simulation_configs.delete_many.
credit_simulation_configs delete-many __none__ system.new_record generated_script
1.9. by-configuration-id
Reads one page of the rows that share a relation value. The relation is part of the address rather than a filter applied after the read.
The command is shaped like this:
credit_simulation_configs by-configuration-id <configuration_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.credit_simulation_configs.list_by_configuration_id.
credit_simulation_configs by-configuration-id 00000000-0000-0000-0000-000000000000 --limit 1
1.10. versions
Reads the row's recorded history, newest first.
The command is shaped like this:
credit_simulation_configs versions <name> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at analytics.v1.credit_simulation_configs_versions.list.
credit_simulation_configs versions __none__ --limit 1
1.11. version
Reads one recorded version of the row.
The command is shaped like this:
credit_simulation_configs version <name> --version <n>
It is addressed at analytics.v1.credit_simulation_configs_versions.get.
credit_simulation_configs version __none__ --version 1