Make store lookups for Events rule jobs request context aware

[whummer]

Make store lookups for Events rule jobs request context aware. This issue surfaced when restoring rule jobs from persistence/pods (companion PR following soon).

At its core, the PR replaces aws_stack.connect_to_service(..) calls with in-memory lookups, and adds EventsStore as a parameter for the get_scheduled_rule_func/put_rule_job_scheduler util methods, to ensure we're targeting the right account/region.

/cc @giograno

Summary of changes:

• pass request context to get_store(..), to extract account/region directly from the context object
• add EventsStore as a parameter for the get_scheduled_rule_func/put_rule_job_scheduler util methods
• add get_event_bus_name(..) util function that extracts the bus name from a name/ARN, or returns the default event bus as a fallback

[github-actions]

LocalStack Community integration with Pro

       2 files         2 suites   1h 32m 38s ⏱️
2 088 tests 1 805 ✔️ 283 💤 0 ❌
2 089 runs  1 805 ✔️ 284 💤 0 ❌

Results for commit 0b1ee21.

♻️ This comment has been updated with latest results.

[coveralls]

coverage: 82.756% (+0.04%) from 82.721% when pulling 0b1ee21 on events-store-ctx into 1d35c60 on master.

[embano1]

@whummer while searching for a solution for my issue (potential bug), I found this PR which is in the same code path. It does not fix my bug, but I wanted to reach out to you since you're familiar with that code base and was wondering whether that's an easy fix you could amend to this PR? #8472

[dominikschubert]

LGTM 👍

[whummer]

Hi @embano1 . The issue you've reported could potentially be resolved with this change: https://github.com/localstack/localstack/pull/8469/files#diff-e93fb0ca12285e3a1b71692d6dcae8cf7333857a6019bbe5af6115615541d088R519-R521 The latest Docker image will be available ~1h after merging this PR, can you then please pull it and give it a try? Thanks!

[embano1]

@whummer you're awesome, will try ASAP and report back in the issue!

[embano1]

@whummer been 3h since you merged and Docker Hub still shows the old one from 7h ago
Is there something broken in CI?

[whummer]

@embano1 , looks like indeed we had some flakiness in our CI pipeline, re-triggered the build one more time, should hopefully update the latest image soon.

You can follow the progress here: https://app.circleci.com/pipelines/github/localstack/localstack?branch=master Thanks

[embano1]

@whummer great, thx a bunch!