anon-ai-toolbelt 0.2.5

Login

Login with your API credentials (writes to ~/.config/anon.ai/config.json):

anon login
> key: ...
> secret: ...

Pipe

Pipe data through to anonymise it:

anon pipe foo.sql result.sql

This parses, analyses and anonymises the data on the fly, i.e.: without persisting it. The data source can be a local filepath or a URL:

anon pipe http://example.com/foo.sql result.sql

You can specify the data format and configure how you’d like it anonymised:

anon pipe foo.sql result.sql --format postgres --config config.json

Note that the anonymisation configuration options are currently unspecified.

Push

Push a data snapshot up to ingest and store it.

anon push foo.dump mydb

Format and source options are the same as with pipe above, e.g.:

anon push http://example.com/foo.sql mydb --format postgres

In this example, mydb is an arbitrary resource name that you use to identify this ingested data source. Subsequent pushes to the same name are usually used to store a new snapshot of the same file or database.

The stored data is encrypted using AES-256 with a per-account encryption key that lives in (and never leaves) a secure vault. You can also optionally provide your own encryption key:

anon push foo.dump mydb --encryption-key LONG_RANDOM_STRING

Note that:

1. your encryption key is never persisted in our system – so you have to manage it and give it to any users that you want to share anonymised data with

2. there’s no strict requirement on length or format for your encryption key value (we SHA-256 hash it along with your per-account encryption key) but we recommend at least 16 bytes entropy

Pull

Pull down an anonymised copy of an ingested data snapshot:

anon pull mydb foo.dump

Optionally provide an encryption key (to decrypt the stored data with) and / or configure how you’d like it anonymised:

anon pull mydb foo.dump --config config.json --encryption-key ...

Locate

As an alternative to pulling down the data locally, you can get a temporary download URL:

anon locate mydb

This writes a temporary url to stdout. As with pull, you can optionally specify an encryption key and configure anonymisation:

anon locate mydb --config config.json --encryption-key ...

You can also control the timeout duration for the URL. This defaults to 30 minutes and can be a maximum of 24 hours:

anon locate mydb --timeout 2h

Analyse

Analyse a snapshot to get our structural analysis of the data:

anon analyse mydb > analysis.json

Inspect

Inspect a resource name to list the versions and see its status:

anon inspect mydb

Versions

You can pull, download and inspect specific snapshot versions by targeting them by name:

anon pull mydb --snapshot someid
anon download mydb --snapshot someid
anon inspect mydb --snapshot someid

You can also push snapshots up with a specific name:

anon push foo.sql mydb --snapshot someid

Tab completion

Enable bash completion by adding the following to your .bashrc:

eval "$(_ANON_COMPLETE=source anon)"

If you use zsh, you can emulate bash completion by first adding bashcompinit to your .zshrc:

autoload bashcompinit
bashcompinit
eval "$(_ANON_COMPLETE=source anon)"

Todo

• better repr results (include type, etc.)

• consistent -o –output formatting i.e. yaml, json

• -v –verbose for logging

• bash and zsh tab complete

• coloured output