-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
EcsRegisterTaskDefinitionOperator params are incorrectly invalidated #29637
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Not a bug Airflow provider, the validation happen inside |
Nevermind, I have a look on wrong parameters initially. |
Ah! yes. I did. Why is that clashing? |
|
This issue has been automatically marked as stale because it has been open for 365 days without any activity. There has been several Airflow releases since last activity on this issue. Kindly asking to recheck the report against latest Airflow version and let us know if the issue is reproducible. The issue will be closed in next 30 days if no further activity occurs from the issue author. |
This issue has been closed because it has not received response from the issue author. |
Apache Airflow Provider(s)
amazon
Versions of Apache Airflow Providers
https://raw.githubusercontent.com/apache/airflow/constraints-2.4.3/constraints-3.10.txt
Apache Airflow version
2.4.3
Operating System
https://github.com/aws/aws-mwaa-local-runner / on macos 12.6
Deployment
Docker-Compose
Deployment details
local
What happened
ECS task definition cpu and memory params are incorrectly invalidated
What you think should happen instead
parameters are correct, it should register a task. I can run the same bit of code using boto3.client.ecs.register_task_definition`
How to reproduce
Try and define a task using:
Could this error have something to do with JSON serialising/deserialising where the parameters are autodetected as
int
s, rather than deserialised into stringsAnything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: