I thought about a specific use case: most of my Terraform codebase is somewhat idempotent. If you don't change anything in the code, after a successful apply all following plan/apply will find no changes to apply.
However I have some specific parts which might change, for example
a datasource for an AWS AMI, which default to the latest AMI available
a datasource containing a list of IP to block in the firewall. This datasource is managed by another team
For these specific changes, which can appear at any time, I would expect Burrito to notify me about this drift. However, I know that I can also blindy apply theses changes since it is common and mastered operations.
For other drifts however, it might be dangerous to apply blindly (for example reverting a manual hotfix in prod) and the planOnly mode of Burrito is more interesting.
I don't have an idea for an interface for this kind of configuration, but being able to have a selective "auto-apply" for know changes would we interesting
I thought about a specific use case: most of my Terraform codebase is somewhat idempotent. If you don't change anything in the code, after a successful apply all following plan/apply will find no changes to apply.
However I have some specific parts which might change, for example
For these specific changes, which can appear at any time, I would expect Burrito to notify me about this drift. However, I know that I can also blindy apply theses changes since it is common and mastered operations.
For other drifts however, it might be dangerous to apply blindly (for example reverting a manual hotfix in prod) and the planOnly mode of Burrito is more interesting.
I don't have an idea for an interface for this kind of configuration, but being able to have a selective "auto-apply" for know changes would we interesting