tirds
tirds is a command-line tool to backup and restore Google Cloud Datastore Entities via local.
tirds stands for Totte IRete DaSu(DataStore).
You can back up Google Cloud Datastore entities, and restore them. Backups are saved to Google Cloud Storage. For details, see Backing Up and Restoring.
But if you move a backup to another bucket, you will not be able to restore it. Because the backup_info file that is metadata of the backup includes the bucket name.
tirds downloads a backup contains backup_info and blob files from the specified bucket, and uploads it to another bucket after replacing the bucket name in the backup_info.
Installation
To install, use pip.
$ pip install tirds
Usage
$ tirds -h
Download backup
Download a backup from Google Cloud Storage.
$ tirds download --out OUTDIR --key-file KEYFILE handle
You can get handle from datastore admin.
KEYFILE is a path to the private key file for Service Account.
Upload backup
Upload a backup to Google Cloud Storage after replacing the bucket name.
$ tirds upload --key-file KEYFILE srcdir bucket
srcdir is a path to the backup.
bucket is a bucket name that is the upload destination and to be replaced with original bucket name.
Metadata
Release files for tirds 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tirds-0.0.2.tar.gz | 4.8 kB | Without provenance | Details for tirds-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tirds-0.0.2-py2-none-any.whl | Python 2 | none | any | Details for tirds-0.0.2-py2-none-any.whl |
Total release size: 14.3 kB
Release files / tirds-0.0.2.tar.gz
| Download URL | tirds-0.0.2.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69d3863b186cdb9a57cd43e3805e0ab59ab0c4a609b40b7aee5644fdbe4e88e7
|
|
BLAKE2b-256 checksum How to use checksums |
47b8bdf5e2d99661d4fc8117340a22ca2ca0da25ae0f0455b6d4a294d7a75ae5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / tirds-0.0.2-py2-none-any.whl
| Download URL | tirds-0.0.2-py2-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
3ef539d97161071568a439c4b6edfee58366d05dd0e9350f7adc22f502066114
|
|
BLAKE2b-256 checksum How to use checksums |
c4283d182489c23eea410e77f9b7b5f1249080403c02c7abdbba494572d27369
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tirds 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.