Adds support for capacity providers to ECS Executor #36722
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:providers
provider:amazon
eladkal
reviewed
Jan 10, 2024
o-nikolas
reviewed
Jan 10, 2024
airflow/providers/amazon/aws/executors/ecs/ecs_executor_config.py
Outdated
Show resolved
Hide resolved
airflow/providers/amazon/aws/executors/ecs/ecs_executor_config.py
Outdated
Show resolved
Hide resolved
o-nikolas
approved these changes
Jan 10, 2024
vincbeck
approved these changes
Jan 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users have asked to be able to use Capacity Provider Strategies instead of the Launch Type (they are mutually exclusive) with the new ECS Executor, so this PR adds that support.
Passes all static checks locally and added unit tests for coverage of new code.
closes: #35489
^ 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.rstor{issue_number}.significant.rst, in newsfragments.