contensis-cli 1.0.0-beta.9 → 1.0.0-beta.90

package/README.md

@@ -1,20 +1,83 @@
 # Contensis CLI
 
-Use Contensis from your favourite terminal with NodeJS
+Use Contensis from your favourite terminal
 
-Install the package via `npm` as a global module
+Download the executable for your operating system from the [Releases page](https://github.com/contensis/node-cli/releases) and add it to a folder in your local `PATH`
+
+or use your preferred installation method below
+
+## Install with package manager
+
+### Windows ([Chocolatey](https://chocolatey.org/install))
+
+```shell
+choco install contensis-cli --pre
+```
+
+- [Choco package docs and source](https://github.com/contensis/node-cli/tree/main/installers/chocolatey)
+- [Contensis CLI on the Chocolatey Community Repository](https://community.chocolatey.org/packages/contensis-cli)
+
+### Mac ([Homebrew](https://docs.brew.sh/Installation))
+
+```shell
+brew tap contensis/cli
+brew install contensis-cli
+```
+
+- [Homebrew tap on GitHub](https://github.com/contensis/homebrew-cli)
+
+### Linux ([Homebrew](https://docs.brew.sh/Homebrew-on-Linux))
 
 ```shell
-npm i contensis-cli --global
+brew tap contensis/cli
+brew install contensis-cli-linux
 ```
 
-## CLI usage
+- [Homebrew tap on GitHub](https://github.com/contensis/homebrew-cli)
+
+## Install as Node.js global module
+
+Install the package via [`npm`](https://www.npmjs.com/package/contensis-cli) as a global module (requires [Node.js](https://nodejs.org/en/download/))
 
 ```shell
-contensis-cli connect example-dev
+npm i --global contensis-cli@prelease
 ```
 
-The CLI uses the same commands and arguments as the shell. It is recommended you use and familiarise yourself with the cli via the shell and use the `contensis-cli` command to use the same cli commands in script-based context such as continuous integration.
+If you use `nvm` and are frequently switching your local `node` version it will also switch your global `node_modules` each time, it is recommended use one of the binary installations instead.
+
+## Install from source
+
+Clone the [repository](https://github.com/contensis/node-cli) and follow the instructions in the [`README`](https://github.com/contensis/node-cli#readme)
+
+# Skip to section
+
+- [Contensis Shell](#contensis-shell)
+- [Use in Terminal](#cli-usage)
+  - [Pass connection details anywhere](#pass-connection-details-anywhere)
+- [Use in Docker](#use-in-docker)
+  - [Run cli commands](#run-cli-commands)
+  - [Persist connections to a local file](#persist-connections-to-a-local-file)
+- [Use in GitLab CI](#use-in-gitlab-ci)
+- [Use in GitHub CI](#use-in-github-ci)
+- [Running headless?](#running-headless-)
+
+## Use in Terminal
+
+Try
+
+```shell
+contensis connect example-dev
+```
+
+or
+
+```shell
+contensis help
+```
+
+The CLI uses exactly the same commands as the shell. It is recommended you use and familiarise yourself with the cli by using the shell and then use the same cli commands when you need to in script-based context such as continuous integration environments.
+
+Launch the [shell](#contensis-shell) by running just the command `contensis`
 
 ### Pass connection details anywhere
 
@@ -31,16 +94,91 @@ You can supply the following options with any command - although they don't appe
  -s  --shared-secret
 ```
 
-### Running headless?
+Using this approach in the cli or the shell will assume these credentials are for your current envioronment and will set the local environment cache for subsequent commands
+
+## Use in Docker
+
+Running the container with the `-it` docker options will launch a shell session
+
+```bash
+docker pull ghcr.io/contensis/node-cli/main/app:latest
+docker run --rm -it ghcr.io/contensis/node-cli/main/app:latest
+```
+
+### Run cli commands
+
+Add the cli command and any options after the container image in the `docker run` command e.g.
+
+```bash
+docker run --rm ghcr.io/contensis/node-cli/main/app:latest get entries "test"
+```
+
+### Persist connections to a local file
+
+To use the cli container for multiple commands or to save connections for future sessions, map a volume to the docker container
+
+<aside>
+⚠️ Ensure a file called `environments.json` exists before mapping the volume to the docker container. If it doesn’t exist, create this empty file first.
+
+</aside>
+
+Linux
+
+```bash
+touch environments.json
+docker run --rm -v $(pwd)/environments.json:/usr/src/app/environments.json -it ghcr.io/contensis/node-cli/main/app:latest
+```
+
+Windows
+
+```powershell
+echo {} > environments.json
+docker run --rm -v ${PWD}/environments.json:/usr/src/app/environments.json -it ghcr.io/contensis/node-cli/main/app:latest
+```
+
+## Use in GitLab CI
+
+```yaml
+push-to-contensis-block:
+  stage: push-to-contensis
+  only:
+    - master
+  image: ghcr.io/contensis/node-cli/main/app:release
+  script:
+    # Create CI/CD Variables in repo settings called CONTENSIS_CLIENT_ID and CONTENSIS_SHARED_SECRET
+    - contensis connect example-dev --project-id website --client-id $CONTENSIS_CLIENT_ID --shared-secret $CONTENSIS_SHARED_SECRET
+    - contensis push block example-website-block $APP_IMAGE:latest --release
+```
+
+## Use in GitHub CI
+
+```yaml
+- name: Push block to Contensis
+  uses: contensis/cli-action@v1
+  with:
+    block-id: example-website-block
+    # auto-release: true # release the block straight away
+    alias: example-dev
+    project-id: website
+    client-id: ${{ secrets.CONTENSIS_CLIENT_ID }} # create secrets for actions
+    shared-secret: ${{ secrets.CONTENSIS_SHARED_SECRET }} # in repo settings
+    tag-repo: true # tag commit with block version
+    git-token: ${{ github.token }} # to allow the git tag
+```
+
+## Running headless?
 
 Most lightweight CI environments will likely not ship with the ability to easily load and unlock an encrypted keychain.
 
-In these environments you will see a warning message when using the cli with any credentials
+In these environments you will see a warning message when using the cli with any credentials, in most cases this type of envioronment is normally disposed of after the command/session has completed and the warning can be safely ignored.
 
 ```shell
   [WARN] Could not connect to local keystore - your password could be stored unencrypted!
 ```
 
+> **Note**
+> There is a workaround for installing a secret store and launching an X11 session with an unlocked keyring which has been left in here below for anyone who wishes to try it
+
 ~~The required credentials to run commands are stored and read from a secret store `libsecret`. Without the secret store running and unlocked we receive an error `Cannot autolaunch D-Bus without X11 $DISPLAY`~~
 
 ```shell
@@ -82,6 +220,64 @@ Press [TAB] for suggestions
 contensis >
 ```
 
+## Skip to section
+
+- [Get started](#get-started)
+- [Connect to a Contensis Cloud environment](#connect-to-a-contensis-cloud-environment)
+- [Login to a connected Contensis environment](#login-to-a-connected-contensis-environment)
+- [Manage Projects](#manage-projects)
+  - [List projects](#list-projects)
+  - [Set current project](#set-current-project)
+  - [Get project metadata](#get-project-metadata)
+  - [Set project metadata](#set-project-metadata)
+  - [Create a new project](#create-a-new-project)
+- [Content Models](#content-models)
+  - [List content models](#list-content-models)
+  - [Examine a content model](#examine-a-content-model)
+  - [List content types, components](#list-content-types--components)
+  - [Examine a content type or component](#examine-a-content-type-or-component)
+- [Entries](#entries)
+  - [Get entries](#get-entries)
+  - [Get an entry by id](#get-an-entry-by-id)
+  - [Get an entry with all of its dependents](#get-an-entry-with-all-of-its-dependents)
+  - [Get entries with a ZenQL statement](#get-entries-with-a-zenql-statement)
+  - [Choose entry fields to output](#choose-entry-fields-to-output)
+  - [Output results to a file](#output-results-to-a-file)
+- [Format output](#format-output)
+- [Manage API keys](#manage-api-keys)
+  - [List keys](#list-keys)
+  - [Create key](#create-key)
+  - [Remove key](#remove-key)
+- [Manage roles](#manage-roles)
+  - [List roles](#list-roles)
+  - [Create role](#create-role)
+  - [Set role details](#set-role-details)
+  - [Disable role](#disable-role)
+  - [Remove role](#remove-role)
+- [Manage content Blocks](#manage-content-blocks)
+  - [List blocks](#list-blocks)
+  - [Get block](#get-block)
+  - [Get block logs](#get-block-logs)
+  - [Push a block](#push-a-block)
+  - [Execute block actions](#execute-block-actions)
+    - [Release a block version](#release-a-block-version)
+    - [Make a block version live](#make-a-block-version-live)
+    - [Mark a block version as broken](#mark-a-block-version-as-broken)
+    - [Rollback a live block version](#rollback-a-live-block-version)
+- [Manage renderers](#manage-renderers)
+  - [List renderers](#list-renderers)
+- [Manage proxies](#manage-proxies)
+  - [List proxies](#list-proxies)
+- [View webhook subscriptions](#view-webhook-subscriptions)
+- [Import content models](#import-content-models)
+  - [Import from another Contensis environment](#import-from-another-contensis-environment)
+  - [From a file](#from-a-file)
+- [Import entries](#import-entries)
+  - [Import from another Contensis environment](#import-from-another-contensis-environment-1)
+  - [Import from a file](#import-from-a-file-1)
+  - [Import entries further reading](#import-entries-further-reading)
+- [Remove entries](#remove-entries)
+
 ## Get started
 
 Press `[tab]` key at any time to show suggested commands or to attempt to auto-complete the command you are typign
@@ -107,6 +303,8 @@ Example call:
   > connect example-dev
 ```
 
+Just type `help` to show the cli command help
+
 ## Connect to a Contensis Cloud environment
 
 Use the connect command followed by the cloud alias of your environment
@@ -121,9 +319,9 @@ contensis > connect example-dev
 contensis example-dev>
 ```
 
-After connecting you will notice the shell prompt will now contain the current "connected" environment - `contensis example-dev> `
+After connecting you will notice the shell prompt will now contain the current "connected" environment e.g. `contensis example-dev> `
 
-The CMS must be online and available in order to connect to it
+Contensis must be online and available in order to connect to it
 
 ```shell
 contensis > connect exemple-dev
@@ -145,9 +343,13 @@ contensis example-dev> login t.durden
 contensis t.durden@example-dev>
 ```
 
-If you are logging in via a script or service you will likely be using an API key set up in Contensis, you would provide the full credentials with the command `login {clientId} -s {sharedSecret}`
+If you are logging in via a script or service you will likely be using an API key set up in Contensis, you would provide the full credentials with the command `login {clientId} -s {sharedSecret}`.
+
+If you need to skip this step for any reason you could [pass connection details anywhere](#pass-connection-details-anywhere)
 
-## List projects
+## Manage Projects
+
+### List projects
 
 Issuing the command `list projects` will fetch a list of projects from the connected Contensis environment
 
@@ -167,7 +369,7 @@ contensis example-dev> list projects
 [cli]  ℹ  Introduce yourself with "login {username}" or "login {clientId} -s {secret}"
 ```
 
-## Set current project
+### Set current project
 
 Set your current working project with the `set project {projectId}` command
 
@@ -187,7 +389,168 @@ intranet t.durden@example-dev>
 
 You will notice the `contensis` prompt has been updated to show your current connected project
 
-## List content types, components
+### Get project metadata
+
+```shell
+contensis t.durden@example-dev> get project
+
+  id: contensis
+  uuid: 4df681ef-f3bc-3d79-57b8-de3f0570b9b3
+  name: Contensis
+  description:
+  primaryLanguage: en-GB
+  supportedLanguages:
+    en-GB
+  color: cobalt
+
+contensis t.durden@example-dev>
+```
+
+### Set project metadata
+
+Update a project name
+
+```shell
+contensis t.durden@example-dev> set project name "Contensis website"
+[cli] ✅ [example-dev] Updated project contensis
+  id: contensis
+  uuid: 4df681ef-f3bc-3d79-57b8-de3f0570b9b3
+  name: Contensis website
+  description:
+  primaryLanguage: en-GB
+  supportedLanguages:
+    en-GB
+  color: cobalt
+
+contensis t.durden@example-dev>
+```
+
+Update a project's description
+
+```shell
+contensis t.durden@example-dev> set project description "Main product site"
+[cli] ✅ [example-dev] Updated project contensis
+  id: contensis
+  uuid: 4df681ef-f3bc-3d79-57b8-de3f0570b9b3
+  name: Contensis website
+  description: Main product site
+  primaryLanguage: en-GB
+  supportedLanguages:
+    en-GB
+  color: cobalt
+
+contensis t.durden@example-dev>
+```
+
+### Create a new project
+
+```shell
+website t.durden@example-dev> create project testProject "Test project" --supported-languages cy
+[cli] ✅ [example-dev] Created project testProject
+
+[cli] ✅ Available projects:
+
+>> testProject [cy *en-GB]
+    website [*en-GB]
+    wordPressSite [*en-GB]
+
+[cli] ✅ Current project is set to testProject
+
+testProject t.durden@example-dev>
+```
+
+## Content Models
+
+Manage your content models like you are the chosen one
+
+### List content models
+
+```shell
+contensis t.durden@example-dev> list models
+[cli] ✅ [website] Content models [ 19 ]
+
+  - accessibleVideo { required by: 3 }
+  - blogListing { components: 1, contentTypes: 2, references: 33, required by: 4 }
+  - blogPost { components: 2, contentTypes: 6, references: 33, required by: 9 }
+  - callToAction { contentTypes: 9, references: 33, required by: 5 }
+  - category { required by: 1 }
+  - contentPage { components: 5, contentTypes: 6, references: 33, required by: 7 }
+  - externalLink { required by: 2 }
+  - growingConditions { components: 1, references: 1, required by: 1 }
+  - homepage { components: 4, contentTypes: 8, references: 33, required by: 3 }
+  - landingPage { components: 9, contentTypes: 12, references: 33, required by: 7 }
+  - person { required by: 2 }
+  - plant { components: 2, contentTypes: 3, references: 8, required by: 10 }
+  - plantType { required by: 2 }
+  - pot { components: 2, contentTypes: 1, references: 3, required by: 11 }
+  - productListing { components: 1, references: 1, required by: 4 }
+  - review { contentTypes: 3, references: 10, required by: 1 }
+  - siteSettings
+  - tag { required by: 5 }
+
+contensis t.durden@example-dev>
+```
+
+### Examine a content model
+
+A `model` is a complete view of a content type that includes all of its dependents - and the dependents of those dependents
+
+- `contentTypes` are the content types that have content linked to the model directly from this content type
+- `components` are the content types that have content linked to the model directly from this content type
+- `dependencies` is an exhaustive list of dependencies and inner dependents [the values in brackets are the models that have required it to make it a dependency]
+- `dependencyOf` is a list of all the other content types (or components) that reference this content type directly, this model is a dependency of those
+
+```shell
+contensis t.durden@example-dev> get model plant
+[cli] ✅ Content models in contensis:
+
+  id: plant
+  dataFormat: model
+  name:
+    en-GB: Plant
+  description:
+    en-GB: Use this content type to store information about individual plants.
+  contentTypes:
+    growingConditions
+    plantType
+    tag
+  components:
+    externalPromotion
+    plantVariant
+  dependencyOf:
+      callToAction
+      homepage
+      landingPage
+      review
+      button
+      cardRow
+      curatedProductSlider
+      featuredBlogPosts
+      featuredProduct
+      promotedProduct
+  dependencies:
+    growingConditions
+      [plant]
+    plantType
+      [plant]
+    pot
+      [plantVariant]
+    tag
+      [plant, pot]
+    externalPromotion
+      [plant, pot]
+    icon
+      [growingConditions]
+    plantVariant
+      [plant]
+    potVariant
+      [pot]
+
+
+contensis t.durden@example-dev>
+```
+
+### List content types, components
 
 ```shell
 contensis t.durden@example-dev> list contenttypes
@@ -212,12 +575,12 @@ contensis t.durden@example-dev> list contenttypes
   - tag [1 field]
 ```
 
-## Examine a content type or component
+### Examine a content type or component
 
 ```shell
 contensis t.durden@example-dev> get contenttype pot
 [cli] ✅ [website] Content type "pot"
-  uuid: adc051ee-d584-4f2a-ba42-5e6190edadb8
+  uuid: 929a99d2-fe5c-4781-84fa-f5a3738aa96d
   id: pot
   projectId: website
   name:
@@ -226,19 +589,19 @@ contensis t.durden@example-dev> get contenttype pot
   entryTitleField: productName
   entryDescriptionField: description
   fields:
-    productName: string
+    productName**: string
     description: string
-    externalPromotion: object
+    externalPromotion: object<component.externalpromotion>
     colour: string
     material: string
-    potVariant: objectArray
-    primaryImage: object
-    photos: objectArray
-    externalCardImage: object
-    tags: objectArray
+    potVariant: objectArray<component.potvariant>
+    primaryImage: object<image>
+    photos: objectArray<image>
+    externalCardImage: object<image>
+    tags: objectArray<entry, tag>
   defaultLanguage: en-GB
   supportedLanguages:
-    0: en-GB
+    en-GB
   workflowId: contensisEntryBasic
   dataFormat: entry
   groups:
@@ -250,7 +613,9 @@ contensis t.durden@example-dev> get contenttype pot
 contensis t.durden@example-dev>
 ```
 
-## Get entries
+## Entries
+
+### Get entries
 
 Use the `get entries` command
 
@@ -280,7 +645,7 @@ Found 8 entries in [website]
 website t.durden@example-dev>
 ```
 
-## Get an entry by id
+### Get an entry by id
 
 ```shell
 website t.durden@example-dev> get entries --id 7cf921a0-ee4f-4bd6-a3f2-0fb0fe1a2ac8
@@ -299,7 +664,7 @@ Found 1 entries in [website]
 website t.durden@example-dev>
 ```
 
-## Get an entry with all of its dependents
+### Get an entry with all of its dependents
 
 Add the `--dependents` or `-d` flag to your `get entries` command to also find and fetch all dependent (linked) entries, recursively finding and including any dependent entries found inside those dependents.
 
@@ -333,7 +698,7 @@ Found 12 entries in [website]
 website t.durden@example-dev>
 ```
 
-## Get entries with a ZenQL statement
+### Get entries with a ZenQL statement
 
 Use a ZenQL statement to find entries with the `--zenql` or `-q` option, add your statement inside `"double quotes"`. Refer to [ZenQL documentation](https://www.contensis.com/help-and-docs/user-guides/zenql-search) and test your statement for the right results in the Contensis web UI.
 
@@ -374,7 +739,7 @@ Found 21 entries in [website]
 website t.durden@example-dev>
 ```
 
-## Choose entry fields to output
+### Choose entry fields to output
 
 Add the `--fields` or `-f` option to your `get entries` command to limit and order the entry fields that are returned, add the api key of each field to be returned separated by a space
 
@@ -406,7 +771,7 @@ Found 12 entries in [website]
 website t.durden@example-dev>
 ```
 
-## Output results to a file
+### Output results to a file
 
 Use the `--output` or `-o` option followed by the file name you wish for command output to be written to
 
@@ -469,9 +834,12 @@ website t.durden@example-dev>
 ```shell
 website t.durden@example-dev> create key "Test key" "Key to demonstrate cli"
 [cli] ✅ [example-dev] Created API key "Test key"
-  - Test key (Key to demonstrate cli) [2022-07-27 t.durden]
-  - id: af645b8b-fa3b-4196-a1b7-ac035f7598a3
-  - sharedSecret: 1ff8b259423c4be08589a63f180c1bdc-63bd3a4f421c44c2afd0ba61e837d671-6aa9532442f149e6a9a837326a9a98e9
+  - Test key [2022-12-13 t.durden]
+    Key to demonstrate cli
+    id: 05a0922f-53e7-4a19-a92c-c9567dbe3246
+    sharedSecret: 63d2828363f74fc1958f0d60c2306aae-02e8bc50271c479f82dba92a08d3ad16-64b93a3bb8eb4f428a1dddaecc9a84d3
+
+[cli] ⏩ Assign your new key to a role with "set role assignments", or create a new role with "create role"
 
 website t.durden@example-dev>
 ```
@@ -489,7 +857,253 @@ website t.durden@example-dev>
 
 Run `list keys` again and you will see your new API key has been removed from the list of keys
 
-## Manage Content Blocks
+## Manage roles
+
+You can use the cli or shell to manage roles that are used to provide access to resources in your Contensis project
+
+### List roles
+
+```shell
+website t.durden@example-dev> list roles
+[cli] ✅ [example-dev] Retrieved roles
+  - Webinar administrators 058ad55d-bf54-4eb2-b74d-2e8ebd93a400
+      groups: System Administrators, Zengenti Marketing Team
+      users: t.turner, j.smith, s.harris
+      keys: Webinar integration
+      entries:
+        webinar: *
+        formWebinarSignUp: *
+        person: *
+        accessibleVideo: *
+  - Entry Administrators 88babee8-9d65-4bd2-93f7-735e2c016911
+    Users assigned to this role can perform all actions on all entries.
+      groups: System Administrators
+      keys: companySync, Docs import, Development, Content administrator
+      entries:
+        *: *
+  - System content syncing 0eca0043-9b91-462a-3007-c5a5b6e6d15d
+    allows background processes to sync content
+      groups: User Administrators
+      keys: Docs import, companySync, User management
+      entries:
+        *: contensisEntryBasic.*
+  - Media service 16d8947c-7571-4c31-b906-d628de8963a8
+    Create and publish media asset entries
+      keys: block-contensis-media-service
+      entries:
+        mediaAsset: *
+
+website t.durden@example-dev>
+```
+
+### Create role
+
+```shell
+website t.durden@example-dev> create role "Test role" "Role to demonstrate cli"
+[cli] ✅ [example-dev] Created role "Test role"
+
+  id: 1329b3cc-0267-480e-a115-b0beaae8fe5b
+  projectId: website
+  name: Test role
+  description: Role to demonstrate cli
+  enabled: true
+  permissions:
+    webhookSubscriptions:
+    proxies:
+    eventStreams:
+    blocks:
+    renderers:
+    views:
+  assignments:
+
+[cli] ⏩ Give access to your role with "set role assignments", allow your role to do things with "set role permissions"
+
+website t.durden@example-dev>
+```
+
+Run `list roles` again and you will see your new role added to the returned list
+
+### Set role details
+
+#### Assignments
+
+Assign users, groups or keys to your role. We will make assignments using their name or user id for users.
+
+```shell
+website t.durden@example-dev> set role assignments "Test role" --assign-keys "Test key"
+[cli] ✅ [example-dev] Retrieved roles
+[cli]  ℹ  Updating role with details
+
+  assignments:
+  - apiKeys:
+      Test key
+
+[cli] ✅ Succesfully updated role
+
+  id: 1329b3cc-0267-480e-a115-b0beaae8fe5b
+  projectId: website
+  name: Test role
+  description: Role to demonstrate cli
+  enabled: true
+  permissions:
+    webhookSubscriptions:
+    proxies:
+    eventStreams:
+    blocks:
+    renderers:
+    views:
+  assignments:
+    apiKeys:
+      Test key
+
+website t.durden@example-dev>
+```
+
+#### Permissions
+
+Set permissions to give the assignees of your role access to your project resources.
+
+We can set permissions for entries.
+
+```shell
+website t.durden@example-dev> set role permissions "Test role" --content-type-ids simpleContent linkedContent
+[cli] ✅ [example-dev] Retrieved roles
+[cli]  ℹ  Updating role with details
+
+  permissions:
+  - entries:
+      id: simpleContent
+      id: linkedContent
+
+[cli] ✅ Succesfully updated role
+
+  id: 1329b3cc-0267-480e-a115-b0beaae8fe5b
+  projectId: website
+  name: Test role
+  description: Role to demonstrate cli
+  enabled: true
+  permissions:
+    entries:
+    - languages:
+        *
+      id: simpleContent
+      actions:
+        *
+    - languages:
+        *
+      id: linkedContent
+      actions:
+        *
+    webhookSubscriptions:
+    proxies:
+    eventStreams:
+    blocks:
+    renderers:
+    views:
+  assignments:
+    apiKeys:
+      Test key
+
+website t.durden@example-dev>
+```
+
+### Disable role
+
+Disable a role by using the command `set role enabled` with the `--disabled` flag
+
+```shell
+website t.durden@example-dev> set role enabled "Test role" --disabled
+[cli] ✅ [example-dev] Retrieved roles
+[cli]  ℹ  Updating role with details
+
+  enabled: false
+
+[cli] ✅ Succesfully updated role
+
+  id: 1329b3cc-0267-480e-a115-b0beaae8fe5b
+  projectId: website
+  name: Test role
+  description: Role to demonstrate cli
+  enabled: false
+
+website t.durden@example-dev>
+```
+
+Enable the role again by calling the same command without the `--disabled` flag
+
+```shell
+website t.durden@example-dev> set role enabled "Test role"
+[cli] ✅ [example-dev] Retrieved roles
+[cli]  ℹ  Updating role with details
+
+  enabled: true
+
+[cli] ✅ Succesfully updated role
+
+  id: 1329b3cc-0267-480e-a115-b0beaae8fe5b
+  projectId: migratortron
+  name: Test role
+  description: Role to demonstrate cli
+  enabled: true
+
+website t.durden@example-dev>
+```
+
+### Remove role
+
+```shell
+website t.durden@example-dev> remove role "Test role"
+[cli] ✅ [example-dev] Retrieved roles
+[cli] ✅ [example-dev] Deleted role Test role
+
+website t.durden@example-dev>
+```
+
+Run `list roles` again and you will see your new role has been removed from the list of role
+
+## View webhook subscriptions
+
+```shell
+website t.durden@example-dev> list webhooks
+[cli] ✅ [example-dev] Webhook subscriptions:
+  - Test webhook 43969978-f9c1-4ee6-a515-11e0ceaddfeb [2022-12-13 t.durden]
+    [POST] https://webhook.site/dede53b3-f044-4640-8634-5f0061ade5c7
+    headers:
+      test: true
+      credential: 🤐
+    topics: resourceType:entry event:[created updated]
+  - More Testing 52e6bac1-1d81-462e-b483-d22034173cb4 [2022-07-15 b.feaver]
+    [POST] https://webhook.site/cd0e99b5-d658-423c-acf5-47af7dfcaa06
+    topics: resourceType:entry event:[published] contentTypeId:[blogPost]
+
+website t.durden@example-dev>
+```
+
+```shell
+website t.durden@example-dev> get webhook "Slack"
+[cli] ✅ [example-dev] Webhook subscriptions:
+  - Slack 5a8dfee1-238f-44fe-b8aa-4b932099500c [2021-07-28 g.moore]
+    Send a notification to a channel
+    [POST] https://webhook.site/5ac0d1c4-8e2e-42c2-a055-66dc7e04843a
+    topics:
+    - resourceType: entry
+      event:
+        published
+        unpublished
+      contentTypeId:
+        article
+    - resourceType: entry
+      event:
+        workflowStateChanged
+      workflowState:
+        contensisEntryApproval.awaitingApproval
+        contensisEntryApproval.declined
+    templates: entry
+
+website t.durden@example-dev>
+```
+
+## Manage content Blocks
 
 You can manage blocks for any Contensis project using the following commands
 
@@ -536,6 +1150,9 @@ website t.durden@example-dev> get block simple-block master
 website t.durden@example-dev>
 ```
 
+> **Tip**
+> Add a version number or `latest` to the end of your `get block {block-id} {branch} {version}` command to output a complete set of details for that block version
+
 ### Get block logs
 
 ```shell
@@ -554,7 +1171,10 @@ website t.durden@example-dev> get block logs contensis-website master
 website t.durden@example-dev>
 ```
 
-### Push block
+### Push a block
+
+> **Note**
+> It is far simpler doing this in [GitLab CI](#use-in-gitlab-ci) or [GitHub CI Actions](#use-in-github-ci)
 
 ```shell
 website t.durden@example-dev> push block cli-test-block ghcr.io/contensis/contensis-app:build-4359 master --release --commit-id 9ee20333 --commit-message "chore: sample commit message" --commit-datetime 2022-11-03T22:34 --author-email b.macka@zengenti.com --committer-email b.macka@zengenti.com --repository-url https://github.com/contensis/contensis-app.git --provider GitlabSelfHosted
@@ -563,69 +1183,517 @@ website t.durden@example-dev> push block cli-test-block ghcr.io/contensis/conten
 website t.durden@example-dev>
 ```
 
-## Use in Docker
+### Execute block actions
 
-Running the container with the `-it` docker options will launch a shell session
+We can perform certain actions on a specific version of a block with the `execute block action {type}` command
 
-```bash
-docker pull ghcr.io/contensis/node-cli/main/app:latest
-docker run --rm -it ghcr.io/contensis/node-cli/main/app:latest
+To execute an action on a specific block version, first you can find the the latest block version number with `get block {block-id} {branch} latest` or leave out the `latest` argument to see a short list of recent versions.
+
+```shell
+website t.durden@example-dev>get block contensis-website master latest
+[cli] ✅ [example-dev] Block contensis-website in project website:
+  v78 contensis-website
+    state: available
+    released: no
+    status:
+      deployment: deployed
+      workflow: draft
+      running status: available
+      datacentres:
+        hq: available
+        london: available
+        manchester: faulted
+    source:
+      commit: b946c1029c1b35aefee2e1a6b5780ddaf205ee74
+      message: build: syntax [nobuild]
+      committed: [22/11/2022 06:50] t.durden@zengenti.com
+      pushed: [22/11/2022 06:52] Gitlab CI block push
+      https://github.com/contensis/contensis-website/commit/b946c1029c1b35aefee2e1a6b5780ddaf205ee74
+    image:
+      uri: ghcr.io/contensis/contensis-website/main/app
+      tag: latest
+    staging url: https://staging-example-dev.cloud.contensis.com?block-contensis-website-versionstatus=draft
+
+website t.durden@example-dev>
 ```
 
-### Run cli commands
+Add the block version number to the `execute block action {type} {block-id} {version}` command - further examples are below
 
-Add the cli command and any options after the container image in the `docker run` command e.g.
+#### Release a block version
 
-```bash
-docker run --rm ghcr.io/contensis/node-cli/main/app:latest get entries "test"
+To mark a block version as "released"
+
+```shell
+
+website t.durden@example-dev> execute block action release contensis-website 78
+[cli] ✅ [example-dev] Action release on contensis-website in project website requested successfully
+  v78 contensis-website
+    state: available
+    released: [23/11/2022 01:42] n.flatley
+    status:
+      deployment: deployed
+      workflow: released
+      running status: available
+      datacentres:
+        hq: available
+        london: available
+        manchester: faulted
+    source:
+      commit: b946c1029c1b35aefee2e1a6b5780ddaf205ee74
+      message: build: syntax [nobuild]
+      committed: [22/11/2022 06:50] t.durden@zengenti.com
+      pushed: [22/11/2022 06:52] Gitlab CI block push
+      null
+    image:
+      uri: ghcr.io/contensis/contensis-website/main/app
+      tag: latest
+    staging url: https://staging-example-dev.cloud.contensis.com?block-contensis-website-versionstatus=released
+
+website t.durden@example-dev>
 ```
 
-### Persist connections to a local file
+> **Note**
+> you can leave out the `version` argument to release the last pushed version of the block
 
-To use the cli container for multiple commands or to save connections for future sessions, map a volume to the docker container
+#### Make a block version live
 
-<aside>
-⚠️ Ensure a file called `environments.json` exists before mapping the volume to the docker container. If it doesn’t exist, create this empty file first.
+Follow the examples for [releasing a block version](#release-a-block-version) except target your command to this action
 
-</aside>
+```shell
+execute block action makelive {block-id} {version}
+```
 
-Linux
+#### Mark a block version as broken
 
-```bash
-touch environments.json
-docker run --rm -v $(pwd)/environments.json:/usr/src/app/environments.json -it ghcr.io/contensis/node-cli/main/app:latest
+Follow the examples for [releasing a block version](#release-a-block-version) except target your command to this action
+
+```shell
+execute block action markasbroken {block-id} {version}
 ```
 
-Windows
+#### Rollback a live block version
 
-```powershell
-echo {} > environments.json
-docker run --rm -v ${PWD}/environments.json:/usr/src/app/environments.json -it ghcr.io/contensis/node-cli/main/app:latest
+Follow the examples for [releasing a block version](#release-a-block-version) except target your command to this action
+
+```shell
+execute block action rollback {block-id} {version}
 ```
 
-## Use in GitLab CI
+## Manage renderers
 
-```yaml
-push-to-contensis-block:
-  stage: push-to-contensis
-  only:
-    - master
-  image: ghcr.io/contensis/node-cli/main/app:latest
-  script:
-    # - contensis connect zenhub-dev --project-id migratortron --client-id 02c8fae0-1aa6-46d3-a0a4-9674fa7f10f1 --shared-secret 47a52c7755324debbcc984865e87200b-35b17f3d39ae40ee9b118358c4dd1666-a516b7c30ebb449ca26e93157588cd26
-    - contensis push block example-website-block $APP_IMAGE:latest --release -a example-dev -p website -id 02c8fae0-1aa6-46d3-a0a4-9674fa7f10f1 -s 47a52c7755324debbcc984865e87200b-35b17f3d39ae40ee9b118358c4dd1666-a516b7c30ebb449ca26e93157588cd26
+You can manage renderers for any Contensis project using the following commands
+
+### List renderers
+
+### Get a renderer
+
+Append the renderer id to the `get renderer` command e.g. `get renderer contensis-website`
+
+## Manage proxies
+
+You can manage proxies for any Contensis project using the following commands
+
+### List proxies
+
+```shell
+website t.durden@example-dev> list proxies
+[cli] ✅ [example-dev] Retrieved proxies in project website:
+  - Get work requests [4.0] b8b6958f-6ae2-41d5-876a-abc86755fd7b Reverse proxy helpdesk endpoints
+      - language: en-GB
+        server: 10.0.46.200
+        headers.host: account-id.zendesk.com
+        ssl: true
+  - HelpDesk Webservice [5.0] fd04d8ad-b1ec-4b0c-95d9-a7a6aec6d05d Used to support the helpdesk
+      - language: en-GB
+        server: 10.0.46.200
+        headers.host: account-id.zendesk.com
+        ssl: true
+
+website t.durden@example-dev>
 ```
 
-## Use in GitHub CI
+### Get a proxy
 
-```yaml
-- name: Push block to Contensis
-  uses: contensis/cli-action@v1
-  with:
-    block-id: example-website-block
-    # auto-release: true
-    alias: zenhub-dev
-    project-id: contensis
-    client-id: ${{ secrets.CONTENSIS_CLIENT_ID }}
-    shared-secret: ${{ secrets.CONTENSIS_SHARED_SECRET }}
+Append the proxy id to the `get proxy` command e.g. `get proxy b8b6958f-6ae2-41d5-876a-abc86755fd7b`
+
+## Import content models
+
+### Import from another Contensis environment
+
+Connect to your "source" environment, ensure you can fetch the models from this environment first and that these models contain the dependencies you plan on importing to your "target" environment.
+
+Check that the right assets will eventually be imported with the `list models` or `get model {modelIds...}` command
+
+When you are happy the expected models are being returned for your import, you should then `connect` to your "target" environment (and `set project`) and when we are successfully connected to our target project, call the `import models` command, ensuring you add any arguments you used with your `get model` check earlier.
+
+#### Specify a list of models to import
+
+```shell
+website t.durden@example-dev> import models plant --source-alias example-dev --source-project-id leif
+
+  -------------------------------------
+ -- IMPORT PREVIEW --
+
+Content types:
+  - growingConditions [website: no change] v1.0
+      required by: [plant]
+      references: [icon]
+  - plant [website: update] v2.0
+      references: [growingConditions, plantGenus, plantType, tag]
+      diff: ...{'id':'<+>genus','name':{'en-GB':'Genus'},'dataType':'object','dataFormat':'entry','description':{},'default':null,'validations':{'allowedContentTypes':{'contentTypes':['plantGenus'],'message':null}},'editor':null,'groupId':'main'},{'id':'</+>plantVariant','name':{'en-GB':'Plant variant'}...
+  - plantGenus [website: create] v0.1
+      required by: [plant]
+  - plantType [website: no change] v1.0
+      required by: [plant]
+  - pot [website: no change] v2.0
+      required by: [plantVariant]
+      references: [externalPromotion, potVariant, tag]
+  - tag [website: no change] v1.0
+      required by: [plant, pot]
+
+Components:
+  - externalPromotion [website: no change] v1.0
+      required by: [plant, pot]
+  - icon [website: no change] v1.0
+      required by: [growingConditions]
+  - plantVariant [website: no change] v2.0
+      required by: [plant]
+      references: [pot]
+  - potVariant [website: no change] v1.0
+      required by: [pot]
+
+website t.durden@example-dev>
+```
+
+#### Import all models from the source project
+
+```shell
+website t.durden@example-dev> import models --source-alias example-dev --source-project-id leif
+  -------------------------------------
+ -- IMPORT PREVIEW --
+
+Content types:
+  - accessibleVideo [website: no change] v1.0
+      required by: [blogPost, contentPage, landingPage]
+  - alert [website: create] v0.1
+  - blogListing [website: no change] v2.0
+      required by: [button, callToAction, homepage, landingPage]
+      references: [blogPost, callToAction, pageMetadata]
+  - blogPost [website: update] v3.0
+      required by: [blogListing, blogPost, button, callToAction, cardRow, contentPage, featuredBlogPosts, homepage, landingPage]
+      references: [accessibleVideo, blogPost, callToAction, category, externalPromotion, featuredProduct, person, tag]
+      diff: ...
+  - callToAction [website: no change] v2.0
+      required by: [blogListing, blogPost, contentPage, homepage, landingPage]
+      references: [blogListing, blogPost, contentPage, externalLink, homepage, landingPage, plant, pot, productListing]
+  - campus [website: create] v0.1
+  - category [website: no change] v1.0
+      required by: [blogPost, department, listing]
+  - contentPage [website: no change] v2.0
+      required by: [button, callToAction, cardRow, contentPage, featuredBlogPosts, homepage, landingPage]
+      references: [accessibleVideo, blogPost, callToAction, callout, cardRow, contentPage, featuredProduct, formPicker, landingPage, pageMetadata, tag]
+  - department [website: two-pass] v0.1
+      references: [category]
+  - event [website: create] v0.1
+  - externalLink [website: no change] v1.0
+      required by: [button, callToAction]
+  - form [website: create] v0.1
+  - growingConditions [website: no change] v1.0
+      required by: [listing, plant]
+      references: [icon]
+  - homepage [website: update] v2.0
+      required by: [button, callToAction, landingPage]
+      references: [blogListing, blogPost, callToAction, contentPage, curatedProductSlider, filteredProductSlider, landingPage, pageMetadata, plant, pot, productListing, promotedProduct]
+      diff: ...
+  - landingPage [website: update] v2.0
+      required by: [button, callToAction, cardRow, contentPage, featuredBlogPosts, homepage, landingPage]
+      references: [accessibleVideo, blogListing, blogPost, bodyCopy, callToAction, contentBlock, contentPage, curatedProductSlider, featuredBlogPosts, featuredProduct, filteredProductSlider, formPicker, homepage, landingPage, pageMetadata, plant, pot, productListing, promotedProduct, review, tag]
+      diff: ...
+  - listing [website: two-pass] v0.1
+      references: [category, growingConditions, plantType, tag]
+  - newsArticle [website: two-pass] v0.1
+      references: [person]
+  - newsTest [website: two-pass] v0.1
+      references: [person]
+  - person [website: no change] v1.0
+      required by: [blogPost, newsArticle, newsTest, review]
+  - plant [website: update] v2.0
+      required by: [button, callToAction, cardRow, curatedProductSlider, featuredBlogPosts, featuredProduct, homepage, landingPage, promotedProduct, review]
+      references: [externalPromotion, growingConditions, plantGenus, plantType, plantVariant, tag]
+      diff: ...
+  - plantFamily [website: two-pass] v0.1
+      required by: [plantOrder]
+      references: [plantGenus]
+  - plantGenus [website: create] v0.1
+      required by: [plant, plantFamily]
+  - plantOrder [website: two-pass] v0.1
+      references: [plantFamily]
+  - plantType [website: no change] v1.0
+      required by: [filteredProductSlider, listing, plant]
+  - pot [website: no change] v2.0
+      required by: [button, callToAction, cardRow, curatedProductSlider, featuredBlogPosts, featuredProduct, homepage, landingPage, plantVariant, promotedProduct, review]
+      references: [externalPromotion, potVariant, tag]
+  - productListing [website: no change] v1.0
+      required by: [button, callToAction, homepage, landingPage]
+      references: [pageMetadata]
+  - review [website: no change] v2.0
+      required by: [landingPage]
+      references: [person, plant, pot]
+  - siteSettings [website: no change] v1.0
+  - tag [website: no change] v1.0
+      required by: [blogPost, contentPage, landingPage, listing, plant, pot]
+  - testLang [website: create] v0.1
+
+Components:
+  - bodyCopy [website: no change] v1.0
+      required by: [landingPage]
+  - button [website: no change] v2.0
+      required by: [promotedProduct]
+      references: [blogListing, blogPost, contentPage, externalLink, homepage, landingPage, plant, pot, productListing]
+  - callout [website: no change] v1.0
+      required by: [contentPage, event]
+  - cardRow [website: no change] v2.0
+      required by: [contentPage]
+      references: [blogPost, contentPage, landingPage, plant, pot]
+  - contentBlock [website: no change] v1.0
+      required by: [landingPage]
+  - curatedProductSlider [website: no change] v2.0
+      required by: [homepage, landingPage]
+      references: [plant, pot]
+  - externalPromotion [website: no change] v1.0
+      required by: [blogPost, plant, pot]
+  - featuredBlogPosts [website: no change] v2.0
+      required by: [landingPage]
+      references: [blogPost, contentPage, landingPage, plant, pot]
+  - featuredProduct [website: no change] v2.0
+      required by: [blogPost, contentPage, landingPage]
+      references: [plant, pot]
+  - filteredProductSlider [website: no change] v2.0
+      required by: [homepage, landingPage]
+      references: [plantType]
+  - formPicker [website: no change] v1.0
+      required by: [contentPage, landingPage]
+  - icon [website: no change] v1.0
+      required by: [growingConditions]
+  - pageMetadata [website: no change] v1.0
+      required by: [blogListing, contentPage, homepage, landingPage, productListing]
+  - plantVariant [website: no change] v2.0
+      required by: [plant]
+      references: [pot]
+  - potVariant [website: no change] v1.0
+      required by: [pot]
+  - promotedProduct [website: update] v2.0
+      required by: [homepage, landingPage]
+      references: [button, plant, pot]
+      diff: ...
+
+website t.durden@example-dev>
 ```
+
+### Import from a file
+
+```shell
+website t.durden@example-dev> import models --from-file ./content-models.json
+```
+
+The output will be the same as the `import models` examples above
+
+<sup><sub>Add the `--commit` option to make the changes, be very careful using this! There is no going back</sub></sup>
+
+## Import entries
+
+### Import from another Contensis environment
+
+Connect to your "source" environment first, ensure you can fetch the entries you plan on importing from here and your query / filters are working to fetch exactly the data you are expecting with the `get entries` command. Add the `--dependents` option to fetch all of the entries that will eventually be imported.
+
+When you are happy you can fetch only the data you intend to import, connect to the "target" environment (and project) then use the same query as before except with the `import entries` command
+
+```shell
+website t.durden@example-dev> import entries --preserve-guids --zenql "sys.contentTypeId = plant" --source-alias example-dev --source-project-id leif
+  -------------------------------------
+ -- IMPORT PREVIEW --
+[26/11 02:16:29] [INFO] Fetching initial entries in project 'leif'
+ Fetch [leif]                                   >> 100% 21 0.0s/0.0s 100000p/s
+ Fetch [leif]                                 >> 100% 79 0.0s/0.0s Infinityp/s
+ Fetch [leif]                                 >> 100% 13 0.0s/0.0s Infinityp/s
+
+Found 113 entries in leif
+--------------------------------------------
+
+ id                                    contentTypeId      entryTitle                      entryDescrip
+------------------------------------------------------------------------------------------------------
+ 7cf921a0-ee4f-4bd6-a3f2-0fb0fe1a2ac8  plant              Aloe vera                       Every kitche
+ 0d94dbf2-89f8-45fb-96d5-175ae1f382ce  plant              Areca palm                      An easy-to-c
+ 43a60005-ea92-4b32-9af3-79560e48ecec  plant              Boston fern                     Brighten up
+ f0cac96c-39a1-4b85-b14b-e8d7d3d08767  plant              Calathea orbifolia              This beautif
+ d647012b-897e-4b6b-bfb5-b9844ef3d648  plant              Canary Island Date Palm         An easy-to-c
+ b7129080-692c-4550-9e2b-28f8ec978651  plant              Chinese evergreen               Easy to care
+ a3339124-4340-4f31-a209-5a6413a89f15  plant              Chinese money plant             The Chinese
+ 8c284599-b615-40a7-9d26-0ddd586fff51  plant              Dracaena fragrans               A great opti
+ 329e3104-332f-48a4-b43a-de852df796b3  plant              Elephant ear                    Elephant ear
+ 504f7b7f-af03-4711-94ca-07edb90fbe00  plant              Heartleaf philodendron          Native to Ce
+ a9a537e8-5508-4166-878c-d5fcd0d9a723  plant              Maidenhair fern                 Easily ident
+ 9a3cc767-8fc1-4ee5-83e1-63c14a508c69  plant              Parlour palm                    Add a bit of
+ ee488c3b-a3a3-4b9c-a3ad-c5a5bdc7e317  plant              Peace lily                      A classic ch
+ 6a71a864-6f61-471a-8cdd-f80237408666  plant              Pink moth orchid                Why buy cut
+ 50868245-3e53-4d9f-86ed-403593da67f6  plant              Ponytail palm                   Despite its
+ 4f05979f-d8cf-4568-9045-05731a33f243  plant              Spider plant                    Breate easy
+ 76a16c87-5e6d-465b-a343-3f14cf2fea0a  plant              String of nickels               A hanging pl
+ 61a2af3a-332c-453c-b9f6-1851d9b7d936  plant              Swiss cheese plant              Bring laid-b
+ 8174fb53-b955-4e36-8f87-646bf286e396  plant              Variegated snake plant          Snake plants
+ b8aa31da-f993-4d81-a361-94ecd5e42547  plant              White moth orchid               Why buy cut
+ 0d707ffe-f42d-44a6-b839-46156ee7f4f3  plant              Yellow moth orchid              Why buy cut
+ 51390024-f193-436f-8552-646cf77ccfdb  image              aloe-vera-closeup               null
+ c0d4ec16-6de2-4394-aaf4-03a56d343bff  image              aloe-vera-gold-pot              null
+ 3b830d97-e976-467c-a833-1b4abcab65d0  image              areca-palm-in-room              null
+ ed0300b0-e841-4c0f-bd1d-9ecd6bc2a354  image              areca-palm-leaf                 null
+ 00119ef1-c3c4-4a49-9076-27eee5605515  image              areca-palm-plant-collection     null
+ 248e2817-6241-4de7-ac5d-75411be4339d  image              boston-fern-close-up            null
+
+ - and 87 more...
+
+[26/11 02:16:29] [INFO] Finding 113 entries in project 'website'
+ Fetch [website]                                  >> 100% 113 0.2s/0.0s 897p/s
+ Fetch [website]                               >> 100% 4 0.0s/0.0s Infinityp/s
+[26/11 02:16:30] [INFO] Building 66 asset entries
+[26/11 02:16:30] [INFO] Building 47 content entries
+
+37/113 entries to migrate into [website]
+
+ contentTypeId         status     total
+----------------------------------------------
+ plantGenus            error      4
+ growingConditions     update     4
+ plant                 update     21
+ pot                   update     12
+ image                 no change  66
+ plantType             no change  5
+ tag                   no change  1
+----------------------------------------------
+
+ id                                    contentTypeId         status    updates  entryTitle
+------------------------------------------------------------------------------------------------------
+ 98347340-a11c-4ee5-b4e7-1ae3b75496a2  plantGenus            error              Aglaonema
+ fa464489-6476-4694-b3d4-e77d0c00a185  plantGenus            error              Alocasia
+ 309d5fd7-a21f-45a8-8abb-f01f820b8f16  plantGenus            error              Aloe
+ 4ebdcc63-929f-4b06-8848-fe046468a63d  plantGenus            error              Beaucarnea
+ 636b925b-a386-4c56-9f33-96cd99cc391c  growingConditions     update    -1,+0    Likes high humidity
+ 2d80e638-eb0d-4bc5-bc96-42b7b8f20678  growingConditions     update    -1,+0    Needs plenty of light
+ 711251f9-f9c6-473b-8b62-0ec8a0d4978c  growingConditions     update    -1,+0    Partial shade
+ d815819d-61c6-4037-95d3-c503acf52153  growingConditions     update    -1,+0    Prefers dry conditions
+ 7cf921a0-ee4f-4bd6-a3f2-0fb0fe1a2ac8  plant                 update    -1,+0    Aloe vera
+ 0d94dbf2-89f8-45fb-96d5-175ae1f382ce  plant                 update    -1,+0    Areca palm
+ 43a60005-ea92-4b32-9af3-79560e48ecec  plant                 update    -1,+0    Boston fern
+ f0cac96c-39a1-4b85-b14b-e8d7d3d08767  plant                 update    -1,+0    Calathea orbifolia
+ d647012b-897e-4b6b-bfb5-b9844ef3d648  plant                 update    -1,+0    Canary Island Date Pal
+ b7129080-692c-4550-9e2b-28f8ec978651  plant                 update    -1,+0    Chinese evergreen
+ a3339124-4340-4f31-a209-5a6413a89f15  plant                 update    -1,+0    Chinese money plant
+ 8c284599-b615-40a7-9d26-0ddd586fff51  plant                 update    -1,+0    Dracaena fragrans
+ 329e3104-332f-48a4-b43a-de852df796b3  plant                 update    -1,+0    Elephant ear
+ 504f7b7f-af03-4711-94ca-07edb90fbe00  plant                 update    -1,+0    Heartleaf philodendron
+ a9a537e8-5508-4166-878c-d5fcd0d9a723  plant                 update    -1,+0    Maidenhair fern
+ 9a3cc767-8fc1-4ee5-83e1-63c14a508c69  plant                 update    -1,+0    Parlour palm
+ ee488c3b-a3a3-4b9c-a3ad-c5a5bdc7e317  plant                 update    -1,+0    Peace lily
+ 6a71a864-6f61-471a-8cdd-f80237408666  plant                 update    -1,+0    Pink moth orchid
+ 50868245-3e53-4d9f-86ed-403593da67f6  plant                 update    -1,+0    Ponytail palm
+ 4f05979f-d8cf-4568-9045-05731a33f243  plant                 update    -1,+0    Spider plant
+ 76a16c87-5e6d-465b-a343-3f14cf2fea0a  plant                 update    -1,+0    String of nickels
+ 61a2af3a-332c-453c-b9f6-1851d9b7d936  plant                 update    -1,+0    Swiss cheese plant
+ 8174fb53-b955-4e36-8f87-646bf286e396  plant                 update    -1,+0    Variegated snake plant
+
+ - and 15 more...
+
+--------------------------------------------
+[26/11 02:16:30] [OK] Done migrating entries
+
+[cli] ⏩ import from project leif to website
+
+  - growingConditions: 4 [existing: 100%] [needs update: 100%]
+  - image: 66 up to date
+  - plant: 21 [existing: 100%] [needs update: 100%]
+  - plantGenus: 4 [existing: 0%]
+  - plantType: 5 up to date
+  - pot: 12 [existing: 100%] [needs update: 100%]
+  - tag: 1 up to date
+  - totalCount: 37
+  - errors: 1
+
+[cli] ❌ Content type 'plantGenus' does not exist in project 'website'
+
+[cli] ❌ [example-dev] Unable to import entries
+
+website t.durden@example-dev>
+```
+
+### Import from a file
+
+```shell
+website t.durden@example-dev> import entries --preserve-guids --from-file ./content-entries.json
+```
+
+The output will be the same as the previous command
+
+<sup><sub>Add the `--commit` option to make the changes, be very careful using this! There is no going back</sub></sup>
+
+### Import entries further reading
+
+The import commands are made possible by using the `migratortron` library. There is further documentation here:
+
+- [`migratortron` on npmjs](https://www.npmjs.com/package/migratortron)
+- [`contensis-importer` on npmjs](https://www.npmjs.com/package/contensis-importer)
+
+## Remove entries
+
+Delete entries by id
+
+```shell
+website t.durden@example-dev> remove entries a1c25591-8c9b-50e2-96d8-f6c774fcf023 8df914cc-1da1-59d6-86e0-
+8ea4ebd99aaa
+ -- PREVIEW --
+[26/11 02:19:53] [INFO] Fetching initial entries in project 'website'
+ Fetch [website]                                 >> 100% 2 0.0s/0.0s Infinityp/s
+[26/11 02:19:53] [INFO] Done deleting entries
+
+a1c25591-8c9b-50e2-96d8-f6c774fcf023 delete homepage Find the perfect plant
+8df914cc-1da1-59d6-86e0-8ea4ebd99aaa delete pot Milano dipped pot
+
+[cli] ⏩ delete from project website
+
+  - totalCount: 2 [to delete: 2]
+
+[cli] ✅ [example-dev] Will delete entries
+
+[cli] ⏩ Add --commit flag to commit the previewed changes
+
+website t.durden@example-dev>
+```
+
+Delete entries with a supplied zenql statement
+
+```shell
+website t.durden@example-dev> remove entries --zenql "sys.version.created > 2022-11-25 14:00"
+ -- PREVIEW --
+[26/11 02:20:52] [INFO] Fetching initial entries in project 'website'
+ Fetch [website]                                   >> 100% 7 0.0s/0.0s 100000p/s
+[26/11 02:20:53] [INFO] Done deleting entries
+
+a1c25591-8c9b-50e2-96d8-f6c774fcf023 delete homepage Find the perfect plant
+bb850178-c88c-50a6-8bac-844273cb19b8 delete image parlour-palm-white-room
+1553d1c8-7a99-5dcd-b1cb-9a90d4cf1985 delete landingPage New subscription service
+f0b0ef1b-fdd1-52d6-99fc-4439e0c186e6 delete plantGenus Aglaonema
+f8f6ee36-9cc4-5d1e-be62-01ac73590947 delete plantGenus Aloe
+8df914cc-1da1-59d6-86e0-8ea4ebd99aaa delete pot Milano dipped pot
+4efeb0e4-dc19-5f87-ab89-47892b9c4169 delete pot Terra large terracotta pot
+
+[cli] ⏩ delete from project website
+
+  - totalCount: 7 [to delete: 7]
+
+[cli] ✅ [example-dev] Will delete entries
+
+[cli] ⏩ Add --commit flag to commit the previewed changes
+
+website t.durden@example-dev>
+```
+
+<sup><sub>Add the `--commit` option to make the changes, be very careful using this! There is no going back</sub></sup>