Service indexing from Service Module to LLM Module

[matKlju]

AS A Service Administrator
I WANT Active services to be indexed in the LLM Module and failed indexing attempts to be retryable
SO THAT the LLM Module receives the latest Active service data without indexing failures blocking service management.

Description

Implement service indexing integration between Service Module and LLM Module.

Indexing is triggered when a service is moved to Active status. Service Module sends the latest saved service data to the LLM Module and stores the result of the indexing attempt.

Indexing is non-blocking: failure in the LLM Module must not prevent the service from becoming Active.

Manual retry is provided through the Reindex / Indekseeri functionality introduced in the Service Dependency Overview UI task #1148.

Lifecycle rules

• Only Active services are indexed in the LLM Module.
• Moving a service to Active triggers indexing using the latest saved service data.
• Draft and Ready services are not sent for indexing.
• Indexing and service lifecycle status are independent:
  • An indexing failure does not prevent activation.
  • An indexing failure does not deactivate an Active service.
• Manual Reindex does not modify the service or its lifecycle status.
• Reindex always uses the latest saved Active service data.
• Unsaved changes are never sent to the LLM Module.

Acceptance Criteria

• Moving a service to Active triggers a Service Module → LLM Module indexing request.
• The latest saved service data is sent for indexing.
• Indexing status changes to Processing when the indexing request starts.
• Successful indexing changes the status to Success.
• Failed indexing changes the status to Failed.
• Indexing failure does not prevent the service from becoming Active.
• Indexing failure does not modify or remove service data.
• Indexing status is persisted and can be retrieved by the Service Dependency Overview.
• Reindex / Indekseeri triggers a new indexing request for an Active service.
• Reindex uses the latest saved service data.
• Reindex changes the status to Processing, followed by Success or Failed according to the result.
• Failed Reindex leaves the service Active and its data unchanged.
• Multiple/repeated Reindex requests do not create duplicate service records in the LLM Module.
• Service indexing failure is logged and an appropriate error response is returned to the UI.
• Reindexing option is only available for active services.

Related tasks

• API indexing retry from Service Module to LLM Module #996 — API indexing retry from Service Module to LLM Module
• Service Dependency Overview #1148 — Service Dependency Overview / indexing UI