Participant data to be invalidated when details change

[kleyow]

Summary: [quoting-service][account-lookup-service] Cache implementation of participants and GP test collection don't work together when activating and deactivating participants in tests while cache values are high in these services.

Affected tests

• Active and inactive participant - testing-toolkit-test-cases/collections/hub/golden_path/feature_tests/Active_Inactive_participants/active_and_inactive_participant.json
• Active and inactive participant account - testing-toolkit-test-cases/collections/hub/golden_path/feature_tests/Active_Inactive_participants/active_and_inactive_participants_accounts.json
• RESERVE NOTIFICATION POSITIVE - TESTFSP1 TESTFSP2 - testing-toolkit-test-cases/collections/hub/golden_path/feature_tests/post_scenarios/reserve_notification_positive_testfsp1_testfsp2.json

There needs to be some way to invalidate caches in the quoting service and account lookup services after GP tests deactivate a participant so that the services are not working off of stale state in GP tests.

The known issue can be resolved by setting cache expiry very low in lieu of fix

• PARTICIPANT_DATA_EXPIRES_IN_MS in the quoting service
• CENTRAL_SHARED_PARTICIPANT_CACHE_CONFIG.expiresIn in ALS

Severity: (Low, Medium, High)

Priority: (Critical, Medium, Low)

Expected Behavior

Steps to Reproduce 1. 2. 3.

Specifications

• Component (if known):
• Version:
• Platform:
• Subsystem:
• Type of testing:
• Bug found/raised by:

Notes:

• Severity when opened:
• Priority when opened:

[elnyry-sam-k]

Very good find @kleyow ..

There was a discussion around this a while ago - "to invalidate cache" when changes to participants happen, but as this brought about, it wasn't implemented then.

As you rightly said, low expiry times help alleviate the issue but do not fix it directly.

Thanks again!