HotCodePush
Commands

audit-log

List an organization's audit log with hotcodepush audit-log list, filtered by type, actor, actor type, app and an inclusive time window.

hotcodepush audit-log list reads an organization's audit log: one row per recorded action, with its type, who acted and the object it touched. It needs a session from login, not an API token, and --organization <id|name> names the organization.

list

List the organization's audit log, newest first, filtered by type, actor, app and time, on a plan that includes the audit log.

OptionTypeDescription
--actor <id>stringThe user who acted, by id.
--actor-type <type>system | usersystem for the rows no user wrote, user for the rest.
--app <id|name>stringThe app, by id or name, to narrow the log to. Defaults to the whole organization, never to hotcodepush.json's app.
--created-since <time>stringThe earliest row, inclusive: an ISO 8601 timestamp or a duration ago such as 2h or 7d.
--created-until <time>stringThe latest row, inclusive: an ISO 8601 timestamp or a duration ago such as 2h or 7d.
--limit <count>numberHow many to list, at most 100; 50 by default.
--offset <count>numberHow many to skip: the offset the previous page ended with.
--type <type>stringThe type, such as channel.created, or channel.* for every action on the object.
hotcodepush audit-log list --type "channel.*" --created-since 7d
hotcodepush audit-log list --app "My App" --actor 4f2c8a1e-6b3d-4e9f-a7c5-2d8b1e6f3a90 --json

Last updated on

audience

Count the devices a release would reach before you create it with hotcodepush audience get, using the same condition flags as release create.

binary

List and inspect store builds with hotcodepush binary, and the binary create build step that writes the resource file and registers the build.

On this page

list