Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enhancement: calculate large blast radius changes #317

Open
patheard opened this issue Mar 27, 2024 · 1 comment
Open

Enhancement: calculate large blast radius changes #317

patheard opened this issue Mar 27, 2024 · 1 comment

Comments

@patheard
Copy link
Member

Summary

If a TF plan includes a large number of changes, include a warning in the PR comment. This "large number of changes" should have a default value and also be configurable.

The use-case this is attempting to fix is to alert PR reviewers that something unexpected may be occurring.
@patheard patheard self-assigned this Mar 27, 2024
@patheard
Copy link
Member Author

A possible way to do this would be compare the percentage of resources that are going to be changed vs. existing resource count.

@patheard patheard removed their assignment Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@patheard