Moltaro 0.0.44-beta
Release date: 2026-09-07
Managed applications can now prepare and connect their File Protection storage through the Portal-managed lifecycle. Existing installations receive a clear one-time activation procedure, while customer-owned repositories remain intact.
Highlights
Section titled “Highlights”- Portal prepares a separate protected storage bucket for each managed app before delivering its scoped runtime access.
- Enabling File Protection connects the managed repository automatically. An already enabled module can complete that connection with Check after the application’s managed storage configuration has been activated.
- Repository setup reports progress and errors without allowing duplicate submissions while an action is running.
Detailed changes
Section titled “Detailed changes”Managed File Protection
Section titled “Managed File Protection”The Portal-managed application lifecycle prepares both ordinary file storage and separate File Protection storage. Existing active applications also have missing protected storage prepared through reconciliation. Provider credentials remain in the Portal; applications receive scoped access rather than account keys. Storage preparation is coordinated with application removal, and a failed preparation stops access delivery instead of reporting a usable repository.
Module activation reuses the managed repository connection. Repeated activation and Check do not create another repository. A previously configured customer-owned repository is preserved. Custom and on-premise repository setup remains explicit.
Repository setup
Section titled “Repository setup”The managed setup page explains that the platform prepares storage and that Check connects or verifies it. Check and Continue show their busy state and cannot be submitted again while running. Updated copy is available in English, Ukrainian, German, Polish and Spanish. Agent installation instructions identify the current protocol as 2.1.
Database and upgrade impact
Section titled “Database and upgrade impact”No database schema migration is introduced. Normal application operations can create the managed repository binding and scoped-access records in existing tables. This release does not copy, replace or delete the application’s primary file storage or business data.
Managed Apps receive a full runtime replacement, with a short interruption per application. Existing apps without managed protection configuration require an additional one-time controlled Stop and Start after the release. Keep the pre-release recovery points. Rolling back binaries does not remove newly created protected storage or bypass its retention: retained objects must remain intact.
Deployment and operator actions
Section titled “Deployment and operator actions”Publish using ReplaceRuntime, not an update package. The production Portal configuration enables Portal-managed protection storage and uses the existing approved managed-storage account credential references. No provider key is delivered to an application or endpoint Agent.
After the release finishes, activate each existing app that has never received protection configuration through the authenticated Portal:
- Stop one application and wait for its job to complete and its state to become Stopped.
- Start the same application and wait for the completed job, Running state and healthy components. Start prepares storage and delivers and activates scoped access through the Runtime VM agent.
- Verify the managed storage bindings and successful access delivery before moving to the next app. Run these transitions sequentially, outside release execution and other application lifecycle operations.
- For an already enabled File Protection module, use Check to connect its workspace repository and verify Ready before configuring a Source or running protection and restore.
Runtime replacement preserves installed configuration; storage reconciliation alone does not deliver missing runtime access. Restarting only API or Worker does not replace this one-time Portal Stop/Start procedure. Failed activation is not success; inspect the normal operation diagnostics and retry through the supported Portal workflow. Do not patch production configuration or database rows manually.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”No known public API, Package SDK, Agent protocol or database breaking change is introduced relative to 0.0.43-beta. File Protection Agent protocol remains 2.1; Runtime VM agent remains 0.1.45. Production managed Portal now requires the Portal-managed protection configuration supplied by the supported release path. Custom/on-premise customer-owned repositories are not switched automatically.