Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Reduce coupling between generic and AWS specific code #10946

Open
@thrau

Description

@thrau

As part of our efforts to better modularize the localstack codebase, we are pushing to reduce the coupling between generic runtime components, and those that are aws specific.

Ultimately, all aws-specific code should live in localstack.aws, but even individual code files often mix generic and aws concepts.

This issue serves as a way to track all PR related to this refactoring effort.

The lager efforts are:

  • Architecture: Generalize the Runtime concept into localstack.runtime, and migrate away from localstack.services.infra
  • Architecture: Generalize the Service and Service Plugin concept and move it to localstack.services
  • Architecture: Use that as input to remove ASF assumptions from our localstack.state
  • Architecture: Remove AWS assumptions from extensions (although it's not clear how)
  • Refactoring: Move localstack.services to localstack.aws.provider (nice to have)
  • Refactoring: Move aws specific utils localstack.utils.aws

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions