Move the registry to in-memory cache#6481
Merged
Merged
Conversation
- Enhance the logging messages - Minor enhancements
- Replace the logging services - Move services to core plugin - CacheAPIUserAllowRunAs - ManageHosts - ServerAPIClient (aka api-interceptor) - ServerAPIHostEntries (aka ) - UpdateConfigurationFile - UpdateRegistry - Adapt the usage of services in the main and check updates plugin from core plugin - Remove plugin logger from main and core plugins - Remove API endpoint - GET /utils/logs/ui - Remove unused code - Adapt the test suites
…to enhancement/6137-adapt-logging-method
…to enhancement/6137-adapt-logging-method
- Remove GET /utils/logs endpoint - Remove related tests - Remove App logs application
- Create Configuration service - Create ConfigurationStore (backend and frontend side) - Register the plugin settings in the configuration services
…ration service
- API endpoints:
- GET /utils/configuration
- PUT /utils/configuration
- PUT /utils/configuration/files/{key}
- DELETE /utils/configuration/files/{key}
Member
Member
Tostti
suggested changes
Mar 18, 2024
Tostti
left a comment
Contributor
There was a problem hiding this comment.
UI
| Test | Chrome | Firefox | Safari |
|---|---|---|---|
| Go to Server APIs, and add an online API host that can be connected. The data about the cluster name or manager name should appear in the table. | ⚫ | 🟢 | ⚫ |
| Go to Server APIs, and edit an offline API host that can be connected. The data about the cluster name or manager name should appear in the table. | ⚫ | 🟢 | ⚫ |
| Go to Server APIs, and edit an online API host that can not be connected. The data about the cluster name or manager name should not appear in the table. | ⚫ | 🟢 | ⚫ |
| Go to Server APIs, change the cluster name or manager name of an offline API connection, and edit the API connection that can be connected. The new data about the cluster name or manager name should appear in the table. | ⚫ | 🟢 | ⚫ |
| Go to Server APIs, change the cluster name or manager name of an offline API connection, and click on the Refresh button. The new data about the cluster name or manager name should appear in the table. | ⚫ | 🟢 | ⚫ |
| Go to Server APIs, and add an offline API host that can be connected. The data about the cluster name or manager name should not appear in the table. | ⚫ | 🟢 | ⚫ |
| Go to About, it only should display the version and revision of the application. No reference to installation date. | ⚫ | 🟢 | ⚫ |
| Changing run as status | ⚫ | 🔴 | ⚫ |
| Removing an API | ⚫ | 🔴 | ⚫ |
Details
🟢 Go to Server APIs, and add an online API host that can be connected. The data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Safari - ⚫
🟢 Go to Server APIs, and edit an offline API host that can be connected. The data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Safari - ⚫
🟢 Go to Server APIs, and edit an online API host that can not be connected. The data about the cluster name or manager name should not appear in the table.
Chrome - ⚫
Safari - ⚫
🟢 Go to Server APIs, change the cluster name or manager name of an offline API connection, and edit the API connection that can be connected. The new data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Safari - ⚫
🟢 Go to Server APIs, change the cluster name or manager name of an offline API connection, and click on the Refresh button. The new data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Safari - ⚫
🟢 Go to Server APIs, and add an offline API host that can be connected. The data about the cluster name or manager name should not appear in the table.
Chrome - ⚫
Safari - ⚫
🟢 Go to About, it only should display the version and revision of the application. No reference to installation date.
Chrome - ⚫
Safari - ⚫
Member
…com/wazuh/wazuh-kibana-app into enhancement/6387-registry-stateless
Member
Author
Changes
|
7 tasks
…o enhancement/6387-registry-stateless
Contributor
|
Contributor
|
Contributor
|
Member
UI
Details 🟢 Go to Server APIs, and add an online API host that can be connected. The data about the cluster name or manager name should appear in the table.Chrome - 🟢 Firefox - ⚫ Safari - ⚫ 🟢 Go to Server APIs, and edit an offline API host that can be connected. The data about the cluster name or manager name should appear in the table.Chrome - 🟢 Firefox - ⚫ Safari - ⚫ 🟢 Go to Server APIs, and edit an online API host that can not be connected. The data about the cluster name or manager name should not appear in the table.Chrome - 🟢 Firefox - ⚫ Safari - ⚫ 🟢 Go to Server APIs, change the cluster name or manager name of an offline API connection, and edit the API connection that can be connected. The new data about the cluster name or manager name should appear in the table.Chrome - 🟢 Firefox - ⚫ Safari - ⚫ 🟢 Go to Server APIs, change the cluster name or manager name of an offline API connection, and click on the Refresh button. The new data about the cluster name or manager name should appear in the table.Chrome - 🟢 Firefox - ⚫ Safari - ⚫ 🟢 Go to Server APIs, and add an offline API host that can be connected. The data about the cluster name or manager name should not appear in the table.Chrome - 🟢 Firefox - ⚫ Safari - ⚫ |
asteriscos
approved these changes
Apr 3, 2024
Tostti
approved these changes
Apr 3, 2024
1 task
1 task
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


































Description
This pull request moves the registry to an in-memory cache and removes some logic done by the frontend side that should do the backend side.
Changes
service.
instead of cacheAPIUserAllowRunAs
Installation datefrom the About viewthe registry data
Issues Resolved
#6387
Evidence
Test
TEST
With an API connection using an with
run_ascapability enabled withrun_asdisabled, edit the API connection settingrun_asastrue, save. TheRun ascolumn should display therun_asis enabled with acheckContext: @yenienserrano
6387-registry-in-memory-cache
Legend:
⚫: none
🟢: pass
🟡: warning
🔴: fail
⚪: not applicable
UI
Details
⚫ Go to Server APIs, and add an online API host that can be connected. The data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, and edit an offline API host that can be connected. The data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, and edit an online API host that can not be connected. The data about the cluster name or manager name should not appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, change the cluster name or manager name of an offline API connection, and edit the API connection that can be connected. The new data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, change the cluster name or manager name of an offline API connection, and click on the Refresh button. The new data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, and add an offline API host that can be connected. The data about the cluster name or manager name should not appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to About, it only should display the version and revision of the application. No reference to installation date.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
6387-registry-in-memory-cache
Legend:
⚫: none
🟢: pass
🟡: warning
🔴: fail
⚪: not applicable
UI
Details
⚫ Go to Server APIs, and add an online API host that can be connected. The data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, and edit an offline API host that can be connected. The data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, and edit an online API host that can not be connected. The data about the cluster name or manager name should not appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, change the cluster name or manager name of an offline API connection, and edit the API connection that can be connected. The new data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, change the cluster name or manager name of an offline API connection, and click on the Refresh button. The new data about the cluster name or manager name should appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to Server APIs, and add an offline API host that can be connected. The data about the cluster name or manager name should not appear in the table.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
⚫ Go to About, it only should display the version and revision of the application. No reference to installation date.
Chrome - ⚫
Firefox - ⚫
Safari - ⚫
Check List
yarn test:jest