mirror of
https://github.com/vatesfr/xen-orchestra.git
synced 2026-11-09 17:06:13 -06:00
666a99706e
* feat(xo6): add page plugins * improve error summary component * plugin configuration form review * fix(xo6): adapt plugins to master after rebase - FrontXoPlugin keeps the plugin types of @vates/types (strict union since #10588) - tests follow the state checks, task params and loading state of the master backend * chore(xo6): add plugins page to the changelog * fix(xo6): pluralize the examples count and unprefix generic plugin i18n keys * fix(xo6): drop JSDoc from the json-schema form * test(xo6): align the plugin tests with the existing test patterns Component tests mock the plugin jobs and assert their run and arguments instead of the REST requests, job tests mock fetch.util directly with run/validate blocks, composable tests use a local mockJob, and createPlugin gets the factory JSDoc. * refactor(xo6): name the json-schema form conditions and share the object schema guard * refactor(xo6): expose the summary errors from the json-schema form * refactor(xo6): name the plugin save and test steps * fix(xo6): use the delete action icon in the plugin delete buttons * revert(xo6): drop the capitalize prop of UiToggle * refactor(xo6): remove the go-to-first-error button of the plugin configuration * refactor(xo6): use VtsDeleteButton in the plugin configuration deletion * revert(web-core): keep useValidatedForm and useFormSelect as on master The plugin forms focus their first missing field through useJsonSchemaForm, so the error summary and focus-on-validate of useValidatedForm had no consumer and changed the behaviour of the existing forms. * feat(web-core): use the puzzle icon for plugins and the window icon for templates * feat(xo6): plugin load and startup actions in the plugins table, panel and header - Side panel: Load/Unload button + "Enable/Disable load at startup" in more actions, loaded / load at startup as statuses, copiable version and description, no bottom link button - Table: action column (select + quick actions) replaces the select column - Detail head bar: same actions, PluginStateToggles removed - One plugin.change-state job replaces the load and unload jobs; updatePluginAutoload and isPluginLoaded move to xo-plugin.util.ts - useXoPluginUtils no longer exposes description - Shared test helpers: createJobResult, createActionItem, findTooltipContent * feat(xo6): read-only plugin detail page, configuration and test in drawers - Detail page: general info + schema-driven read-only configuration card (VtsColumns) - Configure: primary action in head bar, side panel and table row, opens a drawer - Test: drawer from the more-actions menus; delete configuration in the same menus - Errors follow the app pattern: the drawer stays open on job failure - Delete configuration is blocked while the plugin is loaded (the API rejects it) - Secrets: masked by xo-server's name rule or by the value obfuscated by the API - web-core: VtsActionItems extracted from VtsActionsMenu for menu-slot reuse * feat(xo6): show the plugin Configure action first, next to Load * refactor(xo6): remove the unused ApiErrorAlert, useActionError and api-error utils * refactor(xo6): de-duplicate the plugin drawer composables and test fixtures - one useXoPluginDrawerJob replaces the near-identical configure and test composables - useXoPluginUtils exposes the description and loaded state used by the templates - shared plugin schema fixture and JSON schema item-label test helpers * refactor(xo6): de-duplicate the JSON schema fields and the plugin tests - JsonSchemaInputWrapper holds the input wrapper, message and validation of the input, select and XO object fields - JsonSchemaField wraps the object and array fields in their fieldset, which owns the optional value - shared test helpers for drawers, plugin actions, titles and JSON schema forms * refactor(xo6): reuse @vates/obfuscate and cover the JSON schema select fields - @vates/obfuscate exports isSensitiveParam and ships its types; XO 6 imports it and OBFUSCATED_VALUE instead of copies - tests for the select, XO object field and useXoObjectOptions; drop the select guard that could never run - JsonSchemaValue titles its sections in a computed and checks the secret mask * feat(xo6): show the arrays of a plugin configuration as a list * refactor(xo6): share the plugin route and the item label type, remove the unused required key * docs(lite): add a story for VtsActionItems * feat(xo6): validate the numeric limits, integers and list sizes of the plugin forms The JSON schema form only checked the required fields, so a value under minimum, over maximum, a decimal number for an integer or a list shorter than minItems was only rejected by the server. oneOf is still left to the server. * test(xo6): share the drawer, button and tag test helpers, test the preset application Replaces the local submit, button and tag lookups of the backup repository, plugin, host and VM tests with the src/test helpers, makes PluginMoreActions assert its wiring instead of its mock, and documents the new helpers. * test(xo6): test the plugin form lists, sections, messages and links, extract the property grouping * fix(xo6): do not test a plugin while it is being loaded or unloaded * refactor(xo6): give fetchPut and fetchPatch no default type, like fetchPost * refactor(xo6): identify a missing plugin in the plugin job argument instead of in defineJob * refactor(xo6): remove the unused disabled prop from the JSON schema form * refactor(xo6): detect the plugin secrets in the front only, leave @vates/obfuscate as on master - the secret property names and the obfuscated value are local to XO 6 again, no @vates/obfuscate export, types or release - the backup repository and plugin tests import the obfuscated value from the shared constants * refactor(xo6): use checkboxes instead of toggles in the plugin forms * test(xo6): get a checkbox by its label with a shared test helper * test(xo6): reset the state of the array items when the list is replaced from the outside * refactor(xo6): split the JSON schema form dir into the plugin components, utils, composables and form dirs --------- Co-authored-by: Olivier Floch <olivier.floch@vates.fr>
Xen Orchestra
Manage, Backup and Cloudify your XCP-ng/XenServer infrastructure
XO (Xen Orchestra) is a complete solution to visualize, manage, backup and delegate your XCP-ng (or XenServer) infrastructure. No agent is required for it to work.
It provides a web UI, a CLI and a REST API, while also getting a Terraform provider among other connectors/plugins.
⚡️ Quick start
Log in to your account and use the deploy form available from the Vates website.
📚 Documentation
The official documentation is available at https://docs.xen-orchestra.com/
Documentation updates are deployed automatically once per day.
🚀 Features
- Centralized interface: one Xen Orchestra to rule your entire infrastructure, even across datacenters at various locations
- Administration and management: VM creation, management, migration, metrics and statistics, XO proxies for remote sites… XO will become your best friend!
- Backup & Disaster Recovery: The backup is an essential component for the security of your infrastructure. With Xen Orchestra, select the backup mode that suits you best and protect your VMs and your business. Rolling snapshot, Full backup & replication, incremental backup & replication, mirror backup, S3 support among many other possibilities!
- Cloud Enabler: Xen Orchestra is your cloud initiator for XCP-ng (and XenServer). Group management, resource delegation and easy group administration. The Cloud is yours!
🌍 Translations
Status of XO Lite & XO 6:
Help us translate Xen Orchestra in more languages!
📸 Screenshots
License
AGPL3 © Vates