Antonio
I found other problems: - The `customization.enabled` setting is not used for the `api/logos` endpoint. It means, that if this is disabled, and the user has a customized sidebar logo,...
# Update The `customization.logo.sidebar` setting is changed without requiring reloading the browser tab. Related to https://github.com/wazuh/wazuh-kibana-app/pull/4507#issuecomment-1297271223 > This solves an indirect problem when the `customization.enabled` setting is changed from the...
# Update - This change was reverted https://github.com/wazuh/wazuh-kibana-app/pull/4507#issuecomment-1297354125. The `customization.logo.sidebar` requires reloading the browser tab when this is changed. - Add the reloading browser tab requirement when changing the `customization.enabled`...
## Proposal The previous settings to customize the subpath where the assets were exposed in the plugin platform server are no longer necessary. ### Design specifications The configuration of these...
### Details of the new plugin's settings Due to the new design, the current logo customization will be removed, as file upload was not possible. Also, we want to support...
### Specifications of endpoints to manage the assets Target path: `/assets/custom/images/` > We need to study if it's possible to store the custom assets in a directory that is not...
### UI design The following things have been done: - A file picker input component has been added, linked to the new plugin's settings (custom imagery) - Add image preview,...
### Changes in the specification - The settings related to the image customization should be kept in the plugin's configuration file. #### Tasks - [x] Add back the settings in...
#### Latest changes: - Removed the composition of settings. Now all the settings are retrieved from the configuration file. - Adapted the `getConfiguration` backend service. - Adapted the upload and...
- Refactorized the input components to be reusable. - Uncoupled the preview image and the update button components when custom imagery is used.