Configurable options let clients choose or upgrade parts of their storage plan themselves (at order time and later via Manage > Change Options). The module recognizes an option by its name — when a recognized option is present it overrides the package's own field for that service.

Recognized option names

• bucket_quota — the bucket size. The option value is a plain number of GiB (the module appends the unit itself): value 100 = a 100 GiB quota. This is the option you want for sellable size tiers.
• bucket_privacy — overrides the package visibility (public / private).
• minio_billing_per_use — per-service override of the egress-billing switch (true / false).

Setting up a quota upgrade path

1. Go to Packages > Options and create an option group (e.g. "Storage Options").
2. Add an option named exactly bucket_quota, label "Bucket Quota (GiB)", type drop-down (or quantity), and add the tiers you sell — e.g. values 100, 250, 500, 1000 — each with its price per term.
3. Assign the option group to your storage packages (package edit > Configurable Options tab).

How upgrades behave

• When a client changes the option, the module applies the new quota to the bucket immediately — no reprovisioning, no downtime, data untouched.
• The client's Usage tab actively promotes this: once the bucket passes ~80% full it shows an upgrade card linking straight to the option change page.
• Billing follows the effective quota automatically: the free egress allowance (3× quota) scales with the new quota, and quota alerts use the new limit from the next hourly sample.

Notes

• Downgrades below the currently used space are applied on the server as-is — the bucket simply becomes full/over-quota and new uploads fail until data is removed. Consider only offering upward tiers.
• Option prices are ordinary Blesta pricing — prorations and invoicing follow your normal company settings.