Skip to content
Weik.ioDocs
2026.2
Try Weik.io

Events and the entity store

Weik.io 2026.2

Create event channels with the weikio CLI, and manage the events and entities each environment stores. Video

Watch: The channel: one integration publishes, another reacts, 3:49

The video has one integration publish to a channel and another react to it.

On this page

Event channels are integrations, so you publish them with weikio apply and run them with weikio deploy. The same goes for event sources and event subscriptions.

Each environment keeps its stored events and dead letters for 30 days within its size budgets. When a budget fills, the oldest go first. Channel events count against the events budget. Set that budget with weikio env set --events-bytes.

When an integration can’t handle an event after its last retry, Weik.io keeps the event as a dead letter. Each dead letter shows the integration it failed in and the reason. Once you’ve fixed the cause, send the dead letter back to that integration with weikio deadletters resend, or delete it with weikio deadletters discard.

The entity store keeps the latest value of each entity of a type, within the limits of the type’s policy in each environment.

Commands on this page#

Command What it does
weikio get channels List a project’s event channels with their publishers and readers.
weikio channel create Create an event channel.
weikio channel set Change an event channel.
weikio delete channel Delete an event channel that isn’t deployed, together with its versions. The command also deletes the channel’s own variables and secrets.
weikio rename channel Rename an event channel.
weikio get eventsources List the event sources of a project.
weikio get eventsubscriptions List the event subscriptions of a project.
weikio get streams List the usage and limits of an environment’s event streams and dead letters, and of each entity type’s store.
weikio get record Print a record’s kind and address from its ID.
weikio events list List an environment’s stored events.
weikio events show Print one stored event.
weikio events purge Delete the stored events that match the filters.
weikio deadletters list List the dead letters of an environment.
weikio deadletters show Print one dead letter with its event.
weikio deadletters resend Resend dead letters to the integrations they failed in.
weikio deadletters discard Discard dead letters.
weikio get readers List the readers of the integrations deployed in an environment and how far each has read.
weikio reader skip Skip every event the integration’s reader hasn’t handled yet, so the reader receives only the events published from now on.
weikio reader rewind Deliver a reader’s events again from a sequence number.
weikio events resend Publish stored events again.
weikio entities list List the entities of one type in ID order.
weikio entities get Print one entity.
weikio entities delete Delete one entity.
weikio get entity-store-policies List an environment’s entity types with their policies and usage.
weikio describe entity-store-policy Show an entity type’s policy and usage.
weikio entitystore policy set Create an entity type in an environment, or change its policy.
weikio entitystore policy delete Delete an entity type and its entities from an environment.
weikio rename entity-store-policy Rename an entity type in every environment that has it.

The tables below leave out the flags every command accepts, such as --env and --project, which the CLI reference lists.

weikio get channels#

List a project’s event channels with their publishers and readers.

Terminal
weikio get channels [--project P]

Who can run it: a grant on the project whose role has read.

API: GET /api/v1/projects/{project}/channels.

Also written as weikio get eventchannels.

Terminal
$ weikio get channels --project sandbox
You see
NAME     TYPE   DESCRIPTION   RETENTION   PUBLISHERS   READERS   CLOUDEVENTS
alerts   http   -             30d         -            -         binary
plain    -      -             30d         -            -         -

CLOUDEVENTS shows the content mode of a channel with a sink.

weikio channel create#

Create an event channel.

Terminal
weikio channel create <p>/<name> [--type T] [--param k=v ...] [--cloud-events binary|structured] [--description S] [--retention 30d|0]
Argument or flag What it does
<channel> Sets the new channel’s name, as project/name.
--type <type> Sets the sink kamelet the channel delivers to, without its -sink suffix, such as http. Give ‘’ for no sink.
--param <param> Sets a sink parameter, as key=value. Repeat it for each parameter.
--cloud-events <cloud-events> Sets the CloudEvents content mode the sink receives events in, binary or structured. The default is binary.
--description <description> Sets a description of what the channel is for.
--retention <retention> Sets how long Weik.io keeps events, by default the environment’s 30d. Give 0 to store none.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant on the project whose role has author.

API: PUT /api/v1/configuration.

Also written as weikio create channel.

Terminal
$ weikio apply -f ./finance/events/
You see
Target: https://hub.example, project finance (from finance/project.yaml)
event-channel finance/invoice-created unchanged
event-channel finance/invoice-alerts created (version 0.1.0, built in 14.2 s, delivers to slack)
event-source finance/invoice-files created (version 0.1.0, built in 16.8 s, aws-s3 -> invoice-files)
event-subscription finance/files-to-invoices created (version 0.1.0, built in 15.1 s, invoice-files -> invoice-created)
event-subscription finance/alert-on-invoices created (version 0.1.0, built in 14.9 s, invoice-created -> invoice-alerts)

Nothing new is running yet. To run it:
  weikio deploy -f ./finance/events --env devtest
Terminal
$ weikio deploy -f ./finance/events --env devtest
You see
Target: https://hub.example, project finance (from finance/project.yaml), environment devtest (--env)
Deploying finance/invoice-alerts 0.1.0 (latest) to devtest...
Deploying finance/invoice-files 0.1.0 (latest) to devtest...
Deploying finance/files-to-invoices 0.1.0 (latest) to devtest...
Deploying finance/alert-on-invoices 0.1.0 (latest) to devtest...
deployment devtest/finance/invoice-alerts created (version 0.1.0)
deployment devtest/finance/invoice-files created (version 0.1.0)
deployment devtest/finance/files-to-invoices created (version 0.1.0)
deployment devtest/finance/alert-on-invoices created (version 0.1.0)

weikio channel set#

Change an event channel.

Terminal
weikio channel set <p>/<name> [--type T] [--param k=v ...] [--cloud-events binary|structured] [--description S] [--retention 30d|0]
Argument or flag What it does
<channel> Identifies the channel, as project/name.
--type <type> Sets the sink kamelet the channel delivers to, without its -sink suffix, such as http. Give ‘’ for no sink.
--param <param> Sets a sink parameter, as key=value. Repeat it for each parameter.
--cloud-events <cloud-events> Sets the CloudEvents content mode the sink receives events in, binary or structured. The default is binary.
--description <description> Sets a description of what the channel is for.
--retention <retention> Sets how long Weik.io keeps events, by default the environment’s 30d. Give 0 to store none.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant on the project whose role has author.

API:

  • PUT /api/v1/configuration
  • GET /api/v1/projects/{project}/channels
  • GET /api/v1/environments/{environment}/projects/{project}/deployments

weikio delete channel#

Delete an event channel that isn’t deployed, together with its versions. The command also deletes the channel’s own variables and secrets.

Terminal
weikio delete channel <p>/<name> [-y]
Argument or flag What it does
<channel> Identifies the channel, as project/name.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant on the project whose role has author.

API:

  • GET /api/v1/projects/{project}/integrations/{name}
  • DELETE /api/v1/projects/{project}/integrations/{name}?dryRun=true
  • DELETE /api/v1/projects/{project}/integrations/{name}

Also written as weikio delete eventchannel.

weikio rename channel#

Rename an event channel.

Terminal
weikio rename channel <p>/<name> <new-name>
Argument or flag What it does
<channel> Identifies the channel, as project/name.
<new-name> Sets the new name in the same project.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant on the project whose role has author.

API: GET /api/v1/projects/{project}/integrations/{name}, PATCH /api/v1/projects/{project}/integrations/{name}.

weikio get eventsources#

List the event sources of a project.

Terminal
weikio get eventsources [--project P]

Who can run it: a grant on the project whose role has read.

API: GET /api/v1/projects/{project}/integrations?type=event-source, GET /api/v1/projects/{project}/integrations/{name}/status.

weikio get eventsubscriptions#

List the event subscriptions of a project.

Terminal
weikio get eventsubscriptions [--project P]

Who can run it: a grant on the project whose role has read.

API: GET /api/v1/projects/{project}/integrations?type=event-subscription, GET /api/v1/projects/{project}/integrations/{name}/status.

weikio get streams#

List the usage and limits of an environment’s event streams and dead letters, and of each entity type’s store.

Terminal
weikio get streams [--env E]

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/streams.

weikio get record#

Print a record’s kind and address from its ID.

Terminal
weikio get record <id>
Argument or flag What it does
<id> Identifies the record by its ID. weikio describe and a listing with -o json show the ID, as do an audit record and the admin UI’s detail pages.

Who can run it: any API key, but the command shows only the records the key can read.

API: GET /api/v1/records/{uid}.

weikio events list#

List an environment’s stored events.

Family Events
ev Channel events
hook Webhook receipts
mft Transfer run records
schedule Schedule run records
es Entity store changes
Terminal
weikio events list [<p>/<channel>] [--env E] [--family ev|hook|mft|schedule|es] [--api A] [--integration N] [--type <p>/<type>] [--record-id ID] [--since 1h | --from T --to T] [--before STREAM.SEQ | --after STREAM.SEQ] [--order newest|oldest] [--source <p>/<n>] [--with-body] [--limit N]
Argument or flag What it does
<channel> Identifies the channel, as project/name.
--family <family> Shows only the events of one family, such as ev.
--api <api> Lists the webhook receipts of this API.
--integration <integration> Lists the runs of this transfer or schedule, as project/name.
--type <type> Lists only the entity store changes of this entity type, as project/type.
--record-id <record-id> Lists the events of an integration or API by its ID, deleted or not, including the events it published.
--before <before> Shows the events stored before this position, as stream.seq, such as events.48213.
--after <after> Shows the events stored after this position, as stream.seq, such as events.48213.
--order <order> Sorts the events newest or oldest first. The default is newest first.
--source <source> Shows only the events this integration published, as project/name.
--with-body Prints each event’s body in its row.
--since <since> Sets how far back to read, such as 1h.
--from <from> Sets the start of the window.
--to <to> Sets the end of the window.
--limit <limit> Sets how many events to read, at most 1,000.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/events?family=&channel={p}/{name}&project={p}&api=&integration=&type={p}/{type}&recordUid=&from=&to=&source={p}/{name}&withBody=true&limit=&before=&after=&order=.

Terminal
$ weikio events list finance/invoice-created --env production --since 1h
You see
SEQ     STREAM   TIME                      FAMILY   SOURCE                       AGENT         BYTES   RESEND OF
48211   events   2026-09-16 13:02:11 UTC   ev       finance/erp-invoice-export   agent-fi-02   1204    -
48212   events   2026-09-16 13:03:11 UTC   ev       finance/erp-invoice-export   agent-fi-02   1187    -
48213   events   2026-09-16 13:04:40 UTC   ev       finance/invoice-files        agent-fi-02   2310    -

weikio events show#

Print one stored event.

Terminal
weikio events show [<p>/<channel>] [--env E] [--stream S] --seq N [--raw]
Argument or flag What it does
<channel> Identifies the channel the event belongs to, as project/name.
--stream <stream> Sets the event’s stream as events or entities, which the STREAM column shows. The default is events when you give a channel.
--seq <seq> Identifies the event by its sequence number in its stream.
--raw Prints the body as it was stored.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/streams/{stream}/events/{seq}.

Terminal
$ weikio events show finance/invoice-created --env production --seq 48213
You see
Seq:      48213
Subject:  weikio.data.01k5h2m8q3x7c9d4f6g1j0n2p4.ev.01k5h2n1r6t8v0w2y4z6a8b0c2.01k5h3a7b9d1f3g5h7j9k1m3n5
Time:     2026-09-16 13:04:40 UTC
Source:   finance/invoice-files
Headers:  Content-Type: application/json
          Weikio-Agent-Id: 7c1e...
          Weikio-Source: finance/invoice-files

{
  "invoiceId": "INV-2026-0912",
  ...
}

weikio events purge#

Delete the stored events that match the filters. Use it to remove events before the environment’s retention would, for example a webhook body with personal data.

Weik.io writes each purge to the audit log. If a purge runs longer than 10 minutes, run it again to finish it.

Terminal
weikio events purge [<p>/<channel>] [--env E] [--family ev|hook|mft|schedule|es] [--api A] [--integration N] [--type <p>/<type>] [--record-id ID] [-y]
Argument or flag What it does
<channel> Identifies the channel, as project/name.
--family <family> Removes only the events of one family, such as ev.
--api <api> Removes the webhook receipts of this API.
--integration <integration> Removes the runs of this transfer or schedule, as project/name.
--type <type> Removes only the entity store changes of this entity type, as project/type.
--record-id <record-id> Removes the events of an integration or API by its ID, deleted or not, including the events it published.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has operate in the environment.

API: POST /api/v1/environments/{environment}/streams/{stream}/events/_purge.

weikio deadletters list#

List the dead letters of an environment.

Terminal
weikio deadletters list [<p>/<channel>] [--env E] [--integration P/N | --record-id ID] [--since 1h | --from T --to T] [--before SEQ | --after SEQ] [--order newest|oldest] [--limit N]
Argument or flag What it does
<channel> Identifies the channel the events came from, as project/name.
--integration <integration> Identifies the integration the events failed in, as project/name.
--record-id <record-id> Identifies the integration the events failed in by its ID, deleted or not.
--since <since> Shows the dead letters that failed less than this long ago, such as 1h.
--from <from> Sets the start of the time range in which the dead letters failed.
--to <to> Sets the end of the time range in which the dead letters failed.
--before <before> Shows the dead letters older than this sequence number.
--after <after> Shows the dead letters newer than this sequence number. Give 0 to start from the oldest.
--order <order> Sorts the dead letters newest or oldest first. The default is newest first.
--limit <limit> Sets how many dead letters to read, at most 1,000.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/dead-letters?project={p}&integration={n}&recordUid=&channel={p}/{name}&from=&to=&limit=&before=&after=&order=.

weikio deadletters show#

Print one dead letter with its event.

Terminal
weikio deadletters show --seq N [--env E] [--raw]
Argument or flag What it does
--seq <seq> Identifies the dead letter by its sequence number from the SEQ column.
--raw Prints the event’s body as it was stored.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/dead-letters/{seq}.

weikio deadletters resend#

Resend dead letters, each only to the integration it failed in. Weik.io removes a dead letter once it’s sent.

Terminal
weikio deadletters resend (--seq N [--seq N ...] | [<p>/<channel>] [--integration P/N | --record-id ID] [--since 1h | --from T --to T] | --all) [--env E] [-y]
Argument or flag What it does
<channel> Identifies the channel the events came from, as project/name.
--seq <seq> Resends the dead letter with this sequence number. Repeat it for each dead letter.
--all Resends every dead letter you may act on.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.
--integration <integration> Identifies the integration the events failed in, as project/name.
--record-id <record-id> Identifies the integration the events failed in by its ID, deleted or not.
--since <since> Resends only the dead letters that failed less than this long ago, such as 1h.
--from <from> Sets the start of the time range in which the dead letters failed.
--to <to> Sets the end of the time range in which the dead letters failed.

Who can run it: a grant whose role has operate in the environment.

API:

  • With --seq, GET /api/v1/environments/{environment}/dead-letters/{seq}, then POST /api/v1/environments/{environment}/dead-letters/{seq}/resend for each dead letter
  • With a filter or --all, POST /api/v1/environments/{environment}/dead-letters/_resend?dryRun=true, then POST /api/v1/environments/{environment}/dead-letters/_resend

weikio deadletters discard#

Discard dead letters.

Terminal
weikio deadletters discard (--seq N [--seq N ...] | [<p>/<channel>] [--integration P/N | --record-id ID] [--since 1h | --from T --to T] | --all) [--env E] [-y]
Argument or flag What it does
<channel> Identifies the channel the events came from, as project/name.
--seq <seq> Discards the dead letter with this sequence number. Repeat it for each dead letter.
--all Discards every dead letter you may act on.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.
--integration <integration> Identifies the integration the events failed in, as project/name.
--record-id <record-id> Identifies the integration the events failed in by its ID, deleted or not.
--since <since> Discards only the dead letters that failed less than this long ago, such as 1h.
--from <from> Sets the start of the time range in which the dead letters failed.
--to <to> Sets the end of the time range in which the dead letters failed.

Who can run it: a grant whose role has operate in the environment.

API:

  • With --seq, GET /api/v1/environments/{environment}/dead-letters/{seq}, then DELETE /api/v1/environments/{environment}/dead-letters/{seq} for each dead letter
  • With a filter or --all, POST /api/v1/environments/{environment}/dead-letters/_discard?dryRun=true, then POST /api/v1/environments/{environment}/dead-letters/_discard

weikio get readers#

List the readers of the integrations deployed in an environment and how far each has read.

Terminal
weikio get readers [<p>/<channel>] [--integration <p>/<n>] [--env E] [--project P]
Argument or flag What it does
<channel> Identifies the channel that is read, as project/name or, inside the project, as the name alone.
--integration <integration> Identifies the reading integration, as project/name or, inside the project, as the name alone.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/readers?project={p}&integration={n}&channel={p}/{name}.

weikio reader skip#

Skip every event the integration’s reader hasn’t handled yet, so the reader receives only the events published from now on. Use it when a reader is far behind and those events no longer matter. Before you confirm, the command prints how many events it skips.

Terminal
weikio reader skip <p>/<integration> [--channel C | --transfer T | --schedule S | --type T] [--env E] [-y]
Argument or flag What it does
<integration> Identifies the deployed integration, as project/name.
--channel <channel> Identifies the reader that receives events from this channel, as project/name or, inside the integration’s project, as the name alone.
--transfer <transfer> Identifies the reader that receives this transfer’s records, as project/name or, inside the integration’s project, as the name alone.
--schedule <schedule> Identifies the reader that receives this schedule’s runs, as project/name or, inside the integration’s project, as the name alone.
--type <type> Identifies the reader that receives this entity type’s changes, as project/type or, inside the integration’s project, as the type alone.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has operate in the environment.

API: POST /api/v1/environments/{environment}/projects/{project}/deployments/{name}/readers/skip?channel=&transfer=&schedule=&type=&dryRun=true, POST /api/v1/environments/{environment}/projects/{project}/deployments/{name}/readers/skip?channel=&transfer=&schedule=&type=.

weikio reader rewind#

Deliver a reader’s events again from a sequence number. Use it to process events again from a known point, for example after fixing a bug in the reader. Take the sequence number from the SEQ column of weikio events list.

Terminal
weikio reader rewind <p>/<integration> [--channel C | --transfer T | --schedule S | --type T] --to-seq N [--env E] [-y]
Argument or flag What it does
<integration> Identifies the deployed integration, as project/name.
--channel <channel> Identifies the reader that receives events from this channel, as project/name or, inside the integration’s project, as the name alone.
--transfer <transfer> Identifies the reader that receives this transfer’s records, as project/name or, inside the integration’s project, as the name alone.
--schedule <schedule> Identifies the reader that receives this schedule’s runs, as project/name or, inside the integration’s project, as the name alone.
--type <type> Identifies the reader that receives this entity type’s changes, as project/type or, inside the integration’s project, as the type alone.
--to-seq <to-seq> Delivers the events again from this sequence number, which the SEQ column shows.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has operate in the environment.

API: POST /api/v1/environments/{environment}/projects/{project}/deployments/{name}/readers/rewind?channel=&transfer=&schedule=&type=&toSeq=&dryRun=true, POST /api/v1/environments/{environment}/projects/{project}/deployments/{name}/readers/rewind?channel=&transfer=&schedule=&type=&toSeq=.

weikio events resend#

Publish stored events again. Every reader of the channel receives a resent event, which carries a Weikio-Resend-Of header that refers to the original.

Terminal
weikio events resend [<p>/<channel>] [--env E] [--stream S] --seq N [--seq N ...] [--to <p>/<integration>] [--dry-run] [-y]
Argument or flag What it does
<channel> Identifies the channel, as project/name.
--stream <stream> Sets the event’s stream as events or entities, which the STREAM column shows. The default is events when you give a channel.
--seq <seq> Resends the event with this sequence number. Repeat it for each event.
--to <to> Sends the event only to this integration, as project/name. The default is every integration that receives the event.
--dry-run Prints what would happen and changes nothing.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has operate in the environment.

API: POST /api/v1/environments/{environment}/streams/{stream}/events/{seq}/resend.

Terminal
$ weikio events resend finance/invoice-created --env production --seq 48213 -y
You see
Target: https://hub.example, project finance (argument), environment production (--env)
event 48213 resent as 48397 (Weikio-Resend-Of: 48213)

weikio entities list#

List the entities of one type in ID order.

Terminal
weikio entities list <p>/<type> [--env E] [--updated-since T] [--id-prefix S] [--limit N] [--after ID | --before ID]
Argument or flag What it does
<type> Identifies the entity type, as project/type.
--updated-since <updated-since> Shows the entities updated since this time, such as 1h or 2026-09-01.
--id-prefix <id-prefix> Shows only the entities whose ID starts with this text.
--limit <limit> Sets how many entities to read, at most 1,000.
--before <before> Shows the entities before this ID.
--after <after> Shows the entities after this ID.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/projects/{project}/entities/{type}?updatedSince&idPrefix&limit&before&after.

weikio entities get#

Print one entity.

Terminal
weikio entities get <p>/<type> <id> [--env E] [--revisions]
Argument or flag What it does
<type> Identifies the entity type, as project/type.
<id> Identifies the entity by its ID.
--revisions Prints the entity’s kept revisions, newest first.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/projects/{project}/entities/{type}/{id}.

weikio entities delete#

Delete one entity.

Terminal
weikio entities delete <p>/<type> <id> [--env E] [-y]
Argument or flag What it does
<type> Identifies the entity type, as project/type.
<id> Identifies the entity by its ID.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has operate in the environment.

API: DELETE /api/v1/environments/{environment}/projects/{project}/entities/{type}/{id}.

weikio get entity-store-policies#

List an environment’s entity types with their policies and usage.

Terminal
weikio get entity-store-policies [--env E] [--project P]

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/entity-store, GET /api/v1/environments/{environment}/projects/{project}/entity-store.

weikio describe entity-store-policy#

Show an entity type’s policy and usage.

Terminal
weikio describe entity-store-policy <p>/<type> [--env E]
Argument or flag What it does
<type> Identifies the entity type, as project/type.

Who can run it: a grant whose role has read in the environment.

API: GET /api/v1/environments/{environment}/projects/{project}/entity-store/{type}/policy.

weikio entitystore policy set#

Create an entity type in an environment, or change its policy. The --max-bytes of all the environment’s entity types together can’t exceed its entity store budget. Set that budget with weikio env set --entity-store-bytes.

Terminal
weikio entitystore policy set <p>/<type> [--env E] [--max-bytes SIZE] [--max-age LENGTH] [--history N] [--max-value-bytes SIZE] [-y]
Argument or flag What it does
<type> Identifies the entity type, as project/type.
--max-bytes <max-bytes> Sets the maximum size the type may take, such as 512MiB.
--max-age <max-age> Sets the maximum age of an entity, such as 30d.
--history <history> Sets how many values of an entity Weik.io keeps, counting the current one.
--max-value-bytes <max-value-bytes> Sets the maximum size of one entity, such as 64KiB.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has entity-store-policy in the environment.

API: PUT /api/v1/environments/{environment}/projects/{project}/entity-store/{type}/policy.

Terminal
$ weikio entitystore policy set finance/invoice --env production --max-bytes 512MiB --history 2 -y
You see
Target: https://hub.example, project finance (argument), environment production (--env)
entity-store-policy production/finance/invoice created (maxBytes 512 MiB, history 2, revision 57)
production entity store budget: 512 MiB of 2 GiB allocated

weikio entitystore policy delete#

Delete an entity type and its entities from an environment.

Terminal
weikio entitystore policy delete <p>/<type> [--env E] [-y]
Argument or flag What it does
<type> Identifies the entity type, as project/type.
-y, --yes Skips the confirmation.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has entity-store-policy in the environment.

API: DELETE /api/v1/environments/{environment}/projects/{project}/entity-store/{type}/policy.

weikio rename entity-store-policy#

Rename an entity type in every environment that has it.

Terminal
weikio rename entity-store-policy <p>/<type> <new-name>
Argument or flag What it does
<type> Identifies the entity type, as project/type.
<new-name> Sets the new name.
--reason <reason> Stores a reason for the change with the audit record.

Who can run it: a grant whose role has entity-store-policy in the environment.

API: PATCH /api/v1/projects/{project}/entity-store/{type}.

Exit codes#

The codes match the exit code table in the CLI reference.

Code Meaning
0 The command succeeded.
1 The command stopped without making the change.
2 The command has a usage error.
3 Your key is missing, expired or revoked, or its access doesn’t cover the command.
4 What you named doesn’t exist.
5 The change conflicts with another change.
6 Weik.io couldn’t be reached or wasn’t ready, or it was rate limiting your calls or out of storage. Run the command again later.
8 A document isn’t valid.

See also#

Sign in to the live demo

Sign in with the shared viewer account. It can open every screen of the example projects but can't change anything.

E-mail
viewer@demo.weik.io
Password
try-weikio-live-demo
Open the live demo