Add SOV Remote Configuration Contract Tests

[data-sync-user]

Add contract tests to verify the proper operating condition of SOV remote configuration processing.

Acceptance Criteria

• The test plan bellow is implemented
• The CI contract test job is updated to include the new tests

Test Plan (Scenarios)

Preconditions:

• The following environment variables must be configured as follows:
  • ADM_REFRESH_RATE_SECS → 10 seconds
  • SOV_REFRESH_RATE_SECS → 10 seconds

|Title|Scenario|Behaviour|

|Test Contile Startup with Missing SOV Remote Configuration

• This test case will require being executed in a distinct process|# Upload a valid settings_from_shepherd_latest.json file

1. Start Contile|# The GCS bucket contains only the required ADM configuration file
2. Contile fails to start| |Test Contile Startup with Invalid SOV Remote Configuration 【 highlighted #bf2600 】*【 end highlighted 】 【 highlighted #bf2600 】This test case will require being executed in a distinct process【 end highlighted 】|# Upload a valid settings_from_shepherd_latest.json file and a malformed allocation_file_latest.json file to GCS
3. Start Contile|# The GCS bucket contains required ADM and SOV configuration files
4. Contile fails to start| |Test Contile with Updated SOV Remote Configuration|# Upload a new allocation_file_latest.json file to GCS
5. Wait 11 seconds
6. Send a request to the v1 tiles Contile endpoint|# The GCS bucket contains the new SOV configuration file
7. Contile detects the SOV configuration file change
8. Tiles, with the changes, are returned (Status Code 200)| |Test Contile with Missing SOV Remote Configuration (Includes Recovery)|# Remove the allocation_file_latest.json file from GCS
9. Wait 11 seconds
10. Send a request to the v1 tiles Contile endpoint
11. Upload a valid settings_from_shepherd_latest.json file from GCS
12. Wait 11 seconds
13. Send a request to the v1 tiles Contile endpoint|# The GCS bucket contains the required ADM configuration file, but doesn’t contain the required SOV configuration file
14. Contile detects the SOV configuration file change
15. Tiles, with no changes, are returned (Status Code 200)
16. The GCS bucket contains a valid SOV configuration file
17. Contile detects the SOV configuration file change
18. Tiles, with the changes, are returned (Status Code 200)| |Test Contile with Invalid SOV Remote Configuration (Includes Recovery)|# Upload a malformed allocation_file_latest.json file from GCS
19. Wait 11 seconds
20. Send a request to the v1 tiles Contile endpoint
21. Upload a valid allocation_file_latest.json file from GCS
22. Wait 11 seconds
23. Send a request to the v1 tiles Contile endpoint|# The GCS bucket contains a malformed SOV configuration file
24. Contile detects the SOV configuration file change
25. Tiles, with no changes, are returned (Status Code 200)
26. The GCS bucket contains a valid SOV configuration file
27. Contile detects the SOV configuration file change
28. Tiles, with the changes, are returned (Status Code 200)|

┆Issue is synchronized with this Jira Task ┆Epic: Contile Remote Configuration Contract Tests