Create a PD Google Cloud Storage package in Blesta

Skip to main content
Print

Create a PD Google Cloud Storage package in Blesta

Describe the storage allowance, bucket placement and client controls for an offering before accepting orders. Saving the configuration does not itself create the customer’s bucket or access keys.

Configure the offering

  1. Open Packages → Packages → Add Package.
  2. Choose PD Google Cloud Storage and the intended saved Google Cloud account.
  3. Set Default quota (GB), Default Region, Default max buckets and Default versioning.
  4. Select the Soft notify-only choice under Quota mode, observing the limits below.
  5. Review the client feature controls, terms and your own pricing. Save it in the intended package group.
  6. When ready, add that group to the appropriate order form under Packages → Order Forms.

The reviewed release’s option generator writes a different platform’s product option groups. Start with the package’s fixed settings and obtain guidance for your installed build before configuring manual customer-selectable options. A newer native generation workflow should not be assumed from a general Products label.

Review the intended activation process. Eligible paid pending services depend on Provision Paid Pending Services automation; a manually activated service needs the intended staff action. Saving the package or receiving payment alone does not prove that its bucket and access credentials are ready.

Choose the placement and plan defaults

Choose Default Region deliberately. The module offers single regions and the US, EU and Asia multi-regions; it does not offer dual-region placement through this selector. The saved location applies to new buckets; changing the offering’s default does not migrate an existing bucket.

A customer Region selection takes precedence over the offering’s default. Review the effective checkout value even if a dimension is hidden. Do not equate a location listed by the module with proof of current availability or permissions in the intended project.

Set Default quota (GB) explicitly: blank or zero means unlimited in the module. Set Default max buckets deliberately; the fallback is one. Default versioning determines the initial versioning setting when checkout supplies no override. Versioning can retain chargeable older data; do not assume the usage reading captures the entire provider bill.

Use the verified soft-quota setting

Choose the soft notify-only quota mode for this setup. A storage allowance is not an immediate provider-enforced size cap. Usage collection and notifications depend on successful scheduled work; a displayed sample can be stale and does not prove an email reached the customer.

The reviewed build has differing hard-quota behaviour between its usage and plan-change paths. Obtain guidance from PD Modules support for your installed build before using hard quota with this provider. Do not promise that exceeding a quota consistently pauses only uploads while still allowing the customer to delete files.

Review client controls and global settings

Review Client: Bucket management, Client: Share links and Client: Storage settings. Enable the intended management actions for this offering. Client storage keys are separate from the provider’s service-account JSON key; never show the latter to a customer.

Review the module’s global suspension and termination-retention settings separately under PD Modules → GCS → Settings before accepting live services. These affect existing data and access; do not change them merely to test a new product or package. Retention and purge choices need their own deliberate operational review.

Verify an intended activation

Preview the offering, effective choices and your own pricing. When ready, use the normal authorised provisioning test, recognising that it creates chargeable Google resources. Inspect Clients & Storage, Activity, the resulting bucket and the intended customer credentials. Keep the normal cron and scheduled module jobs running.

Confirm application access separately from the provider account test. If provisioning has an uncertain outcome, reconcile existing resources before retrying. Do not include credential JSON or customer secrets.

See the PD Google Cloud Storage Blesta guide for related setup, or explore PD Google Cloud Storage.

Table of Contents

Get your website online with PD Hosting

UK hosting, domains and support from a real team. From a first site to a full server.

Terms and Conditions  ·  Privacy Policy

PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.

PD Hosting
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.