feat: add idle/auto stop TTLs and master/worker instance flexibility …#65653
Open
sravani-bobbala wants to merge 2 commits intoapache:mainfrom
Open
feat: add idle/auto stop TTLs and master/worker instance flexibility …#65653sravani-bobbala wants to merge 2 commits intoapache:mainfrom
sravani-bobbala wants to merge 2 commits intoapache:mainfrom
Conversation
…policies to Dataproc cluster configuration
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…policies to Dataproc cluster configuration
This pull request adds support for configuring Instance Flexibility Policy and Lifecycle Configuration (specifically idle stop TTL and auto stop time) in the Dataproc
ClusterGenerator.Description
idle_stop_ttlandauto_stop_timeto automatically stop clusters based on inactivity or a specific schedule.These changes allow for more flexible and cost-effective Dataproc cluster management directly from Airflow.
Unit tests have been added to verify that these configurations are correctly generated.
Was generative AI tooling used to co-author this PR?
Generated-by: Antigravity following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.