Summary

Using Config0’s stack , you seamlessly integrate your OpenTofu-based code into small workflows. These workflows can be launched or stacked upon one another. The layering ensures simplicity not only in integrating your OpenTofu code but also in handling complex workflows one layer at a time. OpenTofu solutions with Config0 become repeatable, secure, and portable.

Similar to Docker, the stack layer offers the following benefits:

• Simplicity of use
  • Just like using a Docker image, you leverage pre-configured stacks that provide repeatable and consistent automation through a single entry point.
• Ease of extension
  • Similar to working with a Dockerfile, the Config0 stack can be easily customized and modified one layer at a time. Stacks call and reference other stacks .
• Effortless distribution
  • Like a Docker image, the Config0 stack is portable and shared through public (marketplace) and private repositories.
• Security/Dependent Visualization
  • Resembling a layered filesystem, Config0 stacks are built on top of other stacks — a layering of stacks . This layering allows for visibility into all the components and assets that form the automation. You can audit when, who, and where the downstream stacks and scripts come from.

Authoring

• The majority of OpenTofu-based workflows consist of asset types such as execgroups and stack. They utilize the helper method newStack and the built-in Python module TFConstructor.
• Additional asset types like shellouts and actions, as well as the multistage helper class newSchedStack, can be used in other workflows.