Terraform depends_on: Model Hidden Dependencies Without Hiding the Graph
Use depends_on for hidden dependencies, understand conservative plans and data-source deferral, and avoid confusing ordering with readiness.
tag
13 posts
Use depends_on for hidden dependencies, understand conservative plans and data-source deferral, and avoid confusing ordering with readiness.
Use Terraform dynamic blocks for repeated provider-defined nested blocks, distinguish them from for_each resources, and keep module interfaces understandable.
Design predictable module interfaces with precise object types, optional attributes, null handling, and validations that explain caller mistakes.
Control Terraform module source changes with exact registry versions or immutable Git commits, and understand why the provider lock file does not pin modules.
Preserve Terraform-managed objects through address refactors with moved blocks, reviewed plans, instance mappings, and durable module upgrade history.
Build repeatable Terraform module tests with plan and apply runs, provider mocks, input matrices, assertions, and explicit controls for real infrastructure.
Manage FreeBSD loadable kernel modules with kldload, kldstat, and kldunload; distinguish runtime tests from boot loading and diagnose busy or mismatched KLDs.
Design Nushell modules with explicit exports, predictable imports, submodules, and overlays that can be activated, scoped, inspected, and hidden.
Diagnose PowerShell module discovery by separating installed and loaded modules, inspecting PSModulePath, and resolving commands unambiguously.
Use a PowerShell module manifest to declare compatibility, dependencies, exports, and version metadata, then validate the packaged module.
Predict PowerShell variable and function lookup across child scopes, script files, modules, dot-sourcing, and jobs without accidental global state.
Use WSL 2's documented module-loading settings carefully, distinguish module names from a modules VHD, and verify the shared guest kernel.
Building or selecting a compatible WSL 2 kernel, configuring .wslconfig correctly, and keeping a working path back to Microsoft's default kernel.