Fix Azure Spot Containers unhealthy loop issue #47023

[oli2tup]

Fixes: #47023

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[bugraoz93]

Thanks for the changes! Could you please include a unit test case for this new addition? Since we now have a new condition, it is worth checking.

[oli2tup]

Thanks for the changes! Could you please include a unit test case for this new addition? Since we now have a new condition, it is worth checking.

Happy to, are there unit tests already for the Azure Container Instances class? I'm having trouble finding them. If not I'll write some new ones. Thanks

[bugraoz93]

Thanks for the changes! Could you please include a unit test case for this new addition? Since we now have a new condition, it is worth checking.

Happy to, are there unit tests already for the Azure Container Instances class? I'm having trouble finding them. If not I'll write some new ones. Thanks

Nice! Sure, you can find them here https://github.com/apache/airflow/blob/main/providers/microsoft/azure/tests/unit/microsoft/azure/operators/test_container_instances.py. All the providers have their unit tests under their directory and then tests/unit.
providers/<provider_name>/**/tests/unit

[oli2tup]

Thanks for the changes! Could you please include a unit test case for this new addition? Since we now have a new condition, it is worth checking.

Happy to, are there unit tests already for the Azure Container Instances class? I'm having trouble finding them. If not I'll write some new ones. Thanks

Nice! Sure, you can find them here https://github.com/apache/airflow/blob/main/providers/microsoft/azure/tests/unit/microsoft/azure/operators/test_container_instances.py. All the providers have their unit tests under their directory and then tests/unit. providers/<provider_name>/**/tests/unit

Hey, I'm having trouble running the tests even w/o any changes. I've followed the install and testing instructions on the INSTALL markdown but keep getting hit with the below.

ValueError: Cannot resolve 'airflow.sdk.execution_time.secrets_masker.SecretsMasker': No module named 'airflow.sdk'

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.