Subscriptions

Not available in the current build

The configuration described on this page is ignored or rejected by the current version of Specola Core. It is kept for reference only. See Full Configuration for what is supported.

A subscription supplies a complete configuration source that can be refreshed, validated, and activated. It has a different lifecycle and trust boundary from Proxy and Rule Providers.

Create a subscription through the control API with a unique name and trusted file or HTTPS source. Core downloads to managed storage, validates before activation, and preserves the last usable data when a refresh fails. Listing subscriptions reports source, update status, and activation state.

Activating a subscription replaces the active configuration snapshot, so first confirm the new file has safe listener, controller, DNS, and Enhanced settings. Deleting a subscription removes the managed source but must not be treated as a substitute for deactivating or recovering a running profile.

Do not place credentials in URLs where logs or shell history can expose them. Prefer authenticated delivery mechanisms supported by the current API and keep a local recovery configuration. See Providers for reusable node/rule collections and RESTful API for management endpoints.