How do I run the account_operations commands from the shell?
Table of Contents
This file documents declared operations at the shell, one section per command. Every command is a subcommand of account_operations, 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. save-account
Sends save_account_request and prints save_account_response, so the shape is the protocol's and the meaning is the service's. It reads principal, password, totp_secret, email, account_type, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations save-account <principal> <password> <totp_secret> <email> <account_type>
It is addressed at iam.v1.accounts.save.
account_operations save-account __none__ __none__ __none__ __none__ __none__
1.2. update-account
Sends update_account_request and prints update_account_response, so the shape is the protocol's and the meaning is the service's. It reads account_id, email, full_name, default_party_id, job_title, reports_to_account_id, image_id, change_reason_code, change_commentary, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations update-account <account_id> <email> <full_name> <default_party_id> <job_title> <reports_to_account_id> <image_id> <change_reason_code> <change_commentary>
It is addressed at iam.v1.accounts.update.
account_operations update-account __none__ __none__ __none__ __none__ __none__ __none__ __none__ __none__ __none__
1.3. delete-account
Sends delete_account_request and prints delete_account_response, so the shape is the protocol's and the meaning is the service's. It reads account_id, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations delete-account <account_id>
It is addressed at iam.v1.accounts.delete.
account_operations delete-account __none__
1.4. lock-account
Sends lock_account_request and prints lock_account_response, so the shape is the protocol's and the meaning is the service's. It reads account_ids, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations lock-account <account_ids>
It is addressed at iam.v1.accounts.lock.
account_operations lock-account __none__
1.5. unlock-account
Sends unlock_account_request and prints unlock_account_response, so the shape is the protocol's and the meaning is the service's. It reads account_ids, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations unlock-account <account_ids>
It is addressed at iam.v1.accounts.unlock.
account_operations unlock-account __none__
1.6. reset-password
Sends reset_password_request and prints reset_password_response, so the shape is the protocol's and the meaning is the service's. It reads account_ids, new_password, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations reset-password <account_ids> <new_password>
It is addressed at iam.v1.accounts.reset-password.
account_operations reset-password __none__ __none__
1.7. update-my-email
Sends update_my_email_request and prints update_my_email_response, so the shape is the protocol's and the meaning is the service's. It reads email, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations update-my-email <email>
It is addressed at iam.v1.accounts.update-email.
account_operations update-my-email __none__
1.8. set-my-default-party
Sends set_my_default_party_request and prints set_my_default_party_response, so the shape is the protocol's and the meaning is the service's. It reads party_id, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations set-my-default-party <party_id>
It is addressed at iam.v1.accounts.set-default-party.
account_operations set-my-default-party __none__
1.9. select-party
Sends select_party_request and prints select_party_response, so the shape is the protocol's and the meaning is the service's. It reads party_id, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations select-party <party_id>
It is addressed at iam.v1.accounts.select-party.
account_operations select-party __none__
1.10. switch-party
Sends switch_party_request and prints select_party_response, so the shape is the protocol's and the meaning is the service's. It reads party_id, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations switch-party <party_id>
It is addressed at iam.v1.accounts.switch-party.
account_operations switch-party __none__
1.11. change-password
Sends change_password_request_typed and prints change_password_response, so the shape is the protocol's and the meaning is the service's. It reads current_password, new_password, in that order. The caller must have established a session first.
The command is shaped like this:
account_operations change-password <current_password> <new_password>
It is addressed at iam.v1.accounts.change-password.
account_operations change-password __none__ __none__