How do I run the notification_preferences commands from the shell?
Table of Contents
This file documents the notification_preferences resource at the shell, one section per command. Every command is a subcommand of notification_preferences, 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:
notification_preferences list [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at inbox.v1.notification_preferences.list.
notification_preferences 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:
notification_preferences get <account_id> <kind_code> <channel_code>
It is addressed at inbox.v1.notification_preferences.get.
notification_preferences get 00000000-0000-0000-0000-000000000000 __none__ __none__
1.3. get-many
Reads several rows in one request, one key group per row.
The command is shaped like this:
notification_preferences get-many <account_id> <kind_code> <channel_code>
It is addressed at inbox.v1.notification_preferences.get_many.
notification_preferences get-many 00000000-0000-0000-0000-000000000000 __none__ __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:
notification_preferences add <kind_code> <channel_code> <enabled> <reason> <commentary>
It is addressed at inbox.v1.notification_preferences.put.
notification_preferences add __none__ __none__ false 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:
notification_preferences set <account_id> <kind_code> <channel_code> <enabled> <reason> <commentary> [--version <n>]
It is addressed at inbox.v1.notification_preferences.put.
notification_preferences set 00000000-0000-0000-0000-000000000000 __none__ __none__ false 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:
notification_preferences put-many --count <n> <account_id> <kind_code> <channel_code> <enabled> <reason> <commentary>
It is addressed at inbox.v1.notification_preferences.put_many.
notification_preferences put-many --count 1 00000000-0000-0000-0000-000000000000 __none__ __none__ false 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:
notification_preferences delete <account_id> <kind_code> <channel_code> <reason> <commentary> [--version <n>]
It is addressed at inbox.v1.notification_preferences.delete.
notification_preferences delete 00000000-0000-0000-0000-000000000000 __none__ __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:
notification_preferences delete-many <account_id> <kind_code> <channel_code> <reason> <commentary>
It is addressed at inbox.v1.notification_preferences.delete_many.
notification_preferences delete-many 00000000-0000-0000-0000-000000000000 __none__ __none__ system.new_record generated_script
1.9. by-account-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:
notification_preferences by-account-id <account_id> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at inbox.v1.notification_preferences.list_by_account_id.
notification_preferences by-account-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:
notification_preferences versions <account_id> <kind_code> <channel_code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]
It is addressed at inbox.v1.notification_preferences_versions.list.
notification_preferences versions 00000000-0000-0000-0000-000000000000 __none__ __none__ --limit 1
1.11. version
Reads one recorded version of the row.
The command is shaped like this:
notification_preferences version <account_id> <kind_code> <channel_code> --version <n>
It is addressed at inbox.v1.notification_preferences_versions.get.
notification_preferences version 00000000-0000-0000-0000-000000000000 __none__ __none__ --version 1