Livio Spring 82cd1cee08

fix(service ping): correct endpoint, validate and randomize default interval (#10166) ...

# Which Problems Are Solved

The production endpoint of the service ping was wrong.
Additionally we discussed in the sprint review, that we could randomize
the default interval to prevent all systems to report data at the very
same time and also require a minimal interval.

# How the Problems Are Solved

- fixed the endpoint
- If the interval is set to @daily (default), we generate a random time
(minute, hour) as a cron format.
- Check if the interval is more than 30min and return an error if not.
- Fixed yaml indent on `ResourceCount`

# Additional Changes

None

# Additional Context

as discussed internally

2025-07-04 13:45:15 +00:00

..

mock

feat: implement service ping (#10080)

2025-07-02 13:57:41 +02:00

client.go

feat: implement service ping (#10080)

2025-07-02 13:57:41 +02:00

config.go

feat: implement service ping (#10080)

2025-07-02 13:57:41 +02:00

report.go

feat: implement service ping (#10080)

2025-07-02 13:57:41 +02:00

worker_test.go

fix(service ping): correct endpoint, validate and randomize default interval (#10166)

2025-07-04 13:45:15 +00:00

worker.go

fix(service ping): correct endpoint, validate and randomize default interval (#10166)

2025-07-04 13:45:15 +00:00