What do you guys think of having atmos plugins so ...
# atmos-devr
RB
03/15/2026, 2:23 AMWhat do you guys think of having atmos plugins so each subcommand (validate/describe/terraform/helmfile) can be its own separate repo with its own versioned binary?
This way atmos can be a "shell" of a program and can be extendable e.g. you can do something like this
Copy code
atmos plugin add validate@1.0.0
atmos plugin add terraform@1.2.3
atmos plugin add opentofu@2.0.0
etce
Erik Osterman (Cloud Posse)
03/15/2026, 2:42 AMHave you seen atmos toolchain?
Erik Osterman (Cloud Posse)
03/15/2026, 2:42 AMBut yes, want to move in that direction.
Erik Osterman (Cloud Posse)
03/15/2026, 2:43 AMWe introduced the component registry interface as a step in that direction
Erik Osterman (Cloud Posse)
03/15/2026, 2:43 AMWant to finish refactoring packer, helmfile and terraform to use the component registry
Erik Osterman (Cloud Posse)
03/15/2026, 2:43 AMThen we can start to think about how we can introduce plugins
❤️ 1
j
Jonathan Rose
03/15/2026, 3:40 AMMy vote would be to integrate checkov for terraform plan scanning :)
e
Erik Osterman (Cloud Posse)
03/15/2026, 3:48 AMYa, makes sense. Wonder how plugins can build on other plugins.
Erik Osterman (Cloud Posse)
03/15/2026, 3:48 AMe.g. checkov plugin would work on top of opentofu plugin
Erik Osterman (Cloud Posse)
03/15/2026, 3:49 AMi guess plugins could register with the lifecycle hooks, and could tie into toolchain for dependencies
2 Views