Skip to content

Add cronjob for RAFS-DDM

Type of change

  • Bug Fix
  • Feature

Does this introduce a change in the core logic?

  • [No]

Does this introduce a change in the cloud provider implementation, and if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a change that must be documented in the README.md file?

  • [No]

Updates description?

Add admin cronjob for 2024/07/29 12:33:31 INFO GET https://osdu-glab.msft-osdu-test.org/api/rafs-ddms/dev/sa_records_index

Output:

2024/07/29 12:33:30 INFO Retrieved access secrets correctly
2024/07/29 12:33:30 INFO Retrieving service account token
2024/07/29 12:33:31 INFO GET https://osdu-glab.msft-osdu-test.org/api/rafs-ddms/dev/sa_records_index
2024/07/29 12:33:32 INFO Response Code: 503
2024/07/29 12:33:32 WARN retry #0: unexpected response code 503 != 200
2024/07/29 12:33:37 INFO Response Code: 503
2024/07/29 12:33:37 WARN retry #1: unexpected response code 503 != 200
2024/07/29 12:33:45 INFO Response Code: 503
2024/07/29 12:33:45 WARN retry #2: unexpected response code 503 != 200
2024/07/29 12:34:02 INFO Response Code: 503
2024/07/29 12:34:02 WARN retry #3: unexpected response code 503 != 200
2024/07/29 12:34:36 INFO Response Code: 503

Need to test with working rafs-ddms

Merge request reports