ArticCon 2022 (continued)

So why not just use modules?

With terraform you’re in charge of one thing. And that’s by design.

Terraform performs these high-level operations. You have no say in the matter.

Not necessarily a bad thing, but there are drawbacks.

  1. A lot of code is still duplicated.
    • Throwing things up is still easy, but making a change in many little places is painful and error prone.
  2. The module isn’t always the best abstraction layer.

Previous Next
Back to talks
1. Front Page
2. intro: before we begin
3. intro: my background
4. cloud config
5. cloud config: WebUI
6. cloud config: CLI
7. cloud config: IaC
8. cloud config: cognitive load
9. terraform: at a glance
10. terraform: HCL and usage
11. terraform: modules
12. So why not just use modules?
13. cdktf: enter language bindings
14. cdktf: compatible with terraform
15. schema: configuration
16. schema: networks
17. schema: firewalls
18. schema: peers
19. schema: enforcement
20. etl: for many reasons
21. etl: current and desired state
22. arguments: sidebar
23. etl: implementation
24. etl: additional types
25. etl: facilitating abstractions
26. abstraction: implementation details
27. abstraction: example
28. abstraction: but still concrete
29. types: but why
30. demo: full