The idea
Infrastructure as code records intended resources in versioned configuration. Declarative tools compare desired configuration with known or observed infrastructure through their own mechanisms. Dependencies matter: a service may need a network and identity before it can start. Configuration is not permission to operate on any account.
Worked example
A fictional plan describes a network, a storage resource and a service identity. A reviewer sees their relationships in a diff. The same code run against the wrong account could affect unrelated resources, so environment and credentials require explicit checks.
Try it
Draw three fictional resources and their dependencies. Write names for development and production environments and identify the check that prevents mixing them. Explain which configuration changes need review even if the file is syntactically valid.