4 ms·
I also agree, but I don't have experience with the providers he is using. When working with AWS it will always reapply the terraform configuration. A great us
by shadycuz 5y ago
I also agree, but I don't have experience with the providers he is using.
When working with AWS it will always reapply the terraform configuration.
A great use of this is for account hardening. You can run it daily to make sure it's configured correctly.
- OJFord 5y agoIt would be even better if you could somehow tell it it should have control over the entire account, so that anything (entire resources I mean, not just changed properties) created outside terraform would be destroyed. In terms of API use though I suppose that'd be quite expensive to plan - listing every possible AWS resource (in every region!) for example.
- joombaga 5y agoYou'd have to go per-region first to avoid a major redesign on the provider (the API is also per-region). I can see something like a `controlled_resource_types` list attribute on the provider that you could set to e.g. `[aws_instance]` to inform the provider it needs to compare the list of resources of the specified type to the state.
- OJFord 5y agoTrue. That'd be fine though, if you wanted to be really thorough you could just specify a provider for every region and only actually 'use' the ones you wanted, the others just serving as a dummy to enforce no resources.