-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
add persistence API integration for community services #7785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiny issue with the create_cluster
call, otherwise LGTM! 🚀
LOG.info(f"Restoring domain {domain_name} in region {region}.") | ||
try: | ||
preferred_port = None | ||
if config.OPENSEARCH_ENDPOINT_STRATEGY == "port": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's an interesting problem actually that might bite us in a few other places as well when a feature flag changes between different persistence-enabled runs 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
indeed, already had to disable ports in rds snapshot tests https://github.com/localstack/localstack-ext/pull/1397/files#diff-9554b233d544d2d605d0a8067d419a1adc3ee3dfff6500f6524605217b7aaf65R7-R9
38ccc0a
to
16691a7
Compare
This PR uses the persistence API to integrate community services into the persistence lifecycle. It's "basic" because it doesn't fully add restore functionality for every services.
accept_state_visitor
methods to community services that have an asset directorySAVE_STRATEGY
variable used by the persistence plugin to the configcreate_domain
method that were missing after the last ASF API update /cc @alexrashed