Implement client and endpoints for ICANN MoSAPI #2889
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.
This change introduces a comprehensive client to interact with ICANN's Monitoring System API (MoSAPI). This provides direct, automated access to critical registry health and compliance data, moving Nomulus towards a more proactive monitoring posture.
The implementation is structured in layers for clarity and maintainability:
MosApiClientthat manages communication and authentication with the MoSAPI service using TLS client certificates.ServiceMonitoringClient,DomainMetricaClient) that provide a clean, high-level API for specific MoSAPI features.MosapiAlarmService,MosapiDowntimeService, etc.) to encapsulate business logic and data transformation.MosApiModuleand corresponding Dagger integration to provide all the new components to the application./_dr/mosapi/checkalarm/_dr/mosapi/getServiceState/_dr/mosapi/getServiceDowntime/_dr/mosapi/getMetricaReport/_dr/mosapi/listMetricaReportsThis change is