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
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. The shared experimental adapter base deliberately rejects lifecycle operations, so an extension listing or connection check is not a promise that it can deliver a service. 2