Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/index overview #1698

Open
wants to merge 28 commits into
base: develop
Choose a base branch
from
Open

Feature/index overview #1698

wants to merge 28 commits into from

Conversation

lukavdplas
Copy link
Contributor

@lukavdplas lukavdplas commented Nov 8, 2024

Adds tables for Elasticsearch clusters and indices to the database. Close #1695

The models are not used anywhere yet, but will be useful in #1696. For now, the immediate gain is that admins can see an overview of available indices in the admin site. This is information is also available in Kibana, but it's neat.

screenshot of i-analyzer admin site, showing metadata about an index

Keeping the models in sync is all optional at this point, but can be done as follows:

  • There is a django-admin command, update_index_metadata, which will update servers from the Django settings, and indices for each server. I've added this to the yarn start-back command.
  • The admin site includes an action to update index metadata per server, or update the availability status of a single index.

Changes for deployment

It's not strictly necessary to change anything, but I recommend adding the update_index_metadata command to the startup routine in the deployment script.

@lukavdplas lukavdplas added backend changes to the django backend affects-deployment changes that require an update in the deployment module labels Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-deployment changes that require an update in the deployment module backend changes to the django backend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Represent elasticsearch index in postgres database
1 participant