Support the currently existing features in https://github.com/aws/aws-mwaa-local-runner

[rafidka]

Overview

We want to make sure that customers will have the same features they used to have with https://github.com/aws/aws-mwaa-local-runner.

Acceptance Criteria

Add support for the following features:

• Resetting database
• Testing requirements
• Packaging requirements
• Test startup script

For more information, check this

Additional Info

N/A

[jaklan]

We want to make sure that customers will not have the same features they used to have with

@rafidka You mean "will have", not "will not have", right? 😄

But generally my question is about amazon-mwaa-docker-images vs aws-mwaa-local-runner. Should we still use aws-mwaa-local-runner for running a local instance of MWAA >= 2.9 or rather start switching to this solution? Is aws-mwaa-local-runner going to be archived or these two will exist together and aim different goals?

[rafidka]

We want to make sure that customers will not have the same features they used to have with

@rafidka You mean "will have", not "will not have", right? 😄

Sorry yeah, you are right, I will update the description.

But generally my question is about amazon-mwaa-docker-images vs aws-mwaa-local-runner. Should we still use aws-mwaa-local-runner for running a local instance of MWAA >= 2.9 or rather start switching to this solution? Is aws-mwaa-local-runner going to be archived or these two will exist together and aim different goals?

The aws-mwaa-local-runner will eventually be deprecated, but for now you can continue using it. The only reason we haven't deprecated it yet is there is a couple of functionalities in aws-mwaa-local-runner that we haven't ported yet to this repo, e.g. requirements packaging, etc. Having said that, if this repo currently already fulfills your need, then by all means use it as your new local runner. Take a look at the README and give it a try and see if it does what you need.

[jaklan]

@rafidka get it, thanks for clarification!