embabel sample

Fictional records, loaded into a live world and removable in one move.

embabel sample add hubspot-demo      # a name, a file, or gh:owner/repo
embabel sample list                  # what is loaded, and what is mixed with real records
embabel sample remove hubspot-demo   # that set, and nothing else
embabel sample clear                 # everything fake, before somebody sees the screen

The appliance marks every node a set loads, so removing it is exact rather than a best guess at what came from where. Sample data is the only thing this product deletes — removing a realm leaves its records, and so does deleting a world — which is what makes remove and clear safe to run without reading anything first.

A bare name resolves only inside the embabel-worlds org, the same rule realms follow: a short name in a mailed instruction must not be squattable. owner/name and full URLs work too, and show whose data you are about to load before you load it.

Sets are JSON: this client is stdlib-only and runs on whatever python3 you have, and a YAML dependency would be a package to install before the first command works. A .yml set is read when PyYAML happens to be installed, and says so plainly when it is not.

{ "name": "hubspot-demo", "realm": "hubspot",
  "nodes": [
    {"label": "Company", "id": "acme", "displayName": "Acme Pty",
     "properties": {"website": "https://acme.example", "revenue": 84000}}
  ],
  "edges": [] }

realm is required. It is how a set refuses to load when the realm that gives its types meaning is absent, instead of creating records nothing can interpret.

Loading the same set twice merges rather than duplicates, so a set is safe to re-run when something did not land and there is an audience.