ankra bucket
Create, list, inspect and delete object storage buckets on the organisation’s Hetzner, Scaleway, DigitalOcean or UpCloud credentials. Ankra creates the bucket, verifies it and keeps its access keys; the keys are never printed.ankra bucket create
Create an object storage bucket on one of the organisation’s provider credentials (Hetzner, Scaleway, DigitalOcean or UpCloud). Ankra creates the bucket, verifies it and keeps its access keys; the bucket shows “provisioning” until that finishes. The credential defaults to the only one Ankra can create buckets with, the region to that provider’s usual one (fsn1, fr-par, fra1, europe-1) and the provider-side bucket name to a unique one derived from <name>. Hetzner’s Cloud API cannot mint Object Storage keys. Store the key pair on the Hetzner credential once and every bucket after that needs nothing more, or pass--access-key-id here: the secret key is then prompted for, hidden, so it
stays out of your shell history. --secret-access-key exists for automation;
a value passed that way is recorded wherever the command line is.
Examples:
ankra bucket delete
Stop managing an object storage bucket in Ankra. By default this removes only Ankra’s record of the bucket and the access keys it kept: the bucket and every object in it stay in your cloud account.--destroy-provider-resources also empties and deletes the bucket and removes
the UpCloud object storage service or DigitalOcean Spaces key Ankra created
for it. Everything in the bucket is gone for good. A bucket that is still
being created is always torn down, because the half-finished run may already
have made something billable.