Argo CD ApplicationSet and Git Generator: When Does Pruning Delete Child Applications?

Integration Boundary

The Argo CD ApplicationSet controller pairs with the Git generator to create Application resources from JSON or YAML files stored in a repository path. A single templated ApplicationSet can fan out applications across many target clusters, and the controller reconciles child Applications as the generator source changes.

Deletion Behavior Under Question

The prune mechanism keeps generated Applications aligned with the generator output: when an entry disappears from the Git source file, the corresponding child Application is deleted. What remains unclear is how this behaves under real-world Git activity, such as high-frequency commits, partial pushes, or repository reorganizations that temporarily reduce the number of generated entries.

• What exact conditions trigger pruning when the Git generator source is updated?
• Does the ApplicationSet spec offer native options to delay pruning or require manual approval before child Applications are deleted?
• How does the controller respond if the generator temporarily returns fewer entries than before?