Skip to content
agovena.
agovena.
Get started
Community
Back to marketplace

Marketplace · Module

Provisioning

Turn paid service products into service instances with a provider connection and lifecycle.

About this package

What it does

Turn paid service products into service instances with a provider connection and lifecycle. The provisionable capability separates the selected server connection from product resource settings. Provider-specific APIs belong in extensions, so installing this module alone does not connect a hosting panel. 2

Requirements

Agovena Core ^0.0.1. The manifest declares no additional package dependency. Use the matching Core release and apply the module migrations. 1

Set up the package

Enable the module, apply migrations and configure an eligible provisioning extension. Create the server connection, select provider_key and server_id, and complete provider_settings on the product. Run the queue worker and the scheduled instance polling used by your deployment. Order configuration is snapshotted so fulfillment can refer to the purchased configuration rather than a later product edit.

Operation and failure handling

A provisionable product can be ordered only when its provider Extension is enabled and every required connection field is filled in: on the selected provisioning server, or in the Extension settings when no server is selected. Until then the product stays visible with Currently unavailable to order and Admin shows a warning on the product. This check reads stored settings only. Reachability and capacity are checked against the provider at checkout, before payment.

Pterodactyl and Proxmox VE check and reserve capacity at checkout. Account-based panels (cPanel, DirectAdmin, Plesk, Enhance, VirtFusion, Virtualizor and Convoy) have no capacity pool, so checkout accepts the order without a reservation. The account is created after payment; a provider failure is retried and then shown as failed on the service in Admin.

The queued provisioning job is unique per instance, allows three attempts and only handles pending, failed or provisioning states. Missing or corrupt provider configuration is rejected. Do not repeatedly create new instances after an ambiguous provider response: compare the remote resource and local mapping first. Each provider extension implements its own lifecycle and ownership checks and documents which operations it supports, so check the provider guide. A successful connection check alone does not prove that your panel can deliver the service. 2

Sources

Search documentation

Search guides, commands and API endpoints

What are you looking for?

Documentation