Skip to main content
NEO Object Storage is Biznet GIO’s S3-compatible storage line. For the resource schema and full code, see the Terraform and Pulumi reference pages.

​
Pricing (source: biznetgio.com/pricelist#neo-object-storage)

Public list prices, current as of this writing. Object Storage bills by GB of quota, per month, at whichever cycle you choose (m a q s b t p4 p5); see the billing guide.

​
There is no catalog data source for this at all

This is the one product line in these providers with zero typed catalog information. biznetgio_object_storage.product_id / ObjectStorage.productId is a plain required integer. There is no name, no region field, no quota tier exposed anywhere in the schema:
Notably, the region names in the pricing table above (“Single Region 1”, “Multi Region 2”, and so on) are not a separate input anywhere on the resource - region does not exist as an attribute. Whichever region and quota tier you get is entirely a function of which product_id you pick. There is no region argument to set independently. Neither provider wraps this catalog as a data source, even though the upstream API has the endpoint: GET /object-storages/products. Confirmed by reading both providers’ source directly - the Terraform provider’s DataSources() list only registers biznetgio_object_storage_instances, biznetgio_object_storage_buckets, and biznetgio_object_storage_credentials; none of them call the /products endpoint. The Pulumi provider’s function list is the same, one-to-one.

​
Discover a product_id manually

Match what you see against the region/tier you want from the pricing table above, then hardcode that product_id. This is exactly what the example repo does (product_id = 8) - there is currently no better way. If you place an order through the portal first, the order confirmation or account page there is another way to learn the product_id you were assigned, without calling the API directly.
product_id on biznetgio_object_storage / ObjectStorage is create-only. Changing it does not trigger an upgrade - it destroys and recreates the entire instance, deleting every bucket, credential, and object inside it. Get the right product_id before you apply, not after.
Wrapping GET /object-storages/products as a real biznetgio_object_storage_products data source is a good, contained first contribution, and arguably the highest-value one in either provider - see the Terraform provider guide and Pulumi provider guide.

​
What you can list

Once an instance exists, three data sources give you real information about it:
  • biznetgio_object_storage_instances / objectStorageInstances - every instance on the account (optionally filtered by status), returning id, label, status, product_id, quota, raw per item. This confirms the product_id of instances you already own, but does not help you choose a new one.
  • biznetgio_object_storage_buckets / objectStorageBuckets - buckets inside a given instance (name, acl, raw).
  • biznetgio_object_storage_credentials / objectStorageCredentials - credentials on a given instance (access_key, active - secret keys are never returned by a list).
Full schemas in the Terraform and Pulumi reference pages.