6 Answers
- Newest
- Most votes
- Most comments
5
Hello,
This is currently a known issue from MWAA service side due to a test file import error in the MWAA plugin where the “test_cli.py” file resides and they are currently fixing it. Please note that this issue is only cosmetic and should not cause disruptions to your environments as you also confirmed that all your dags and plugins are working correctly. We will let you know when the change is deployed to production.
0
And same issue with MWAA v. 2.4.3. but only in 1 of 3 environments with the same setup
answered a year ago
0
It doesn't affect your ability to run CLI commands, but ... the error message will be included in all the answers of the CLI calls which is annoying.
I'm using MWAA 2.0.2
answered a year ago
Relevant content
- asked 2 years ago
AWS OFFICIALUpdated 8 months ago- AWS OFFICIALUpdated 10 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hi, It has been 4 days since this answer. We are still facing this banner in our MWAA v. 2.0.2. Any update please?
Hello, The fix is expected to be deployed by 13th of Feb. Rest assured, it will not cause any disruptions to any of the components in MWAA environment as it is just cosmetic. Thanks!
Does this missing plugin currently affect our ability to use "aws mwaa" CLI commands?
I am still seeing this with MWAA v. 2.4.3. Is there any update on when it might be resolved?
Hello, The issue was already fixed on 13 Feb. You are required to update your environment to see it reflect on your UI.