A look at packs
So far, we have explored the structure of a component that is a very standalone object. Once you have modeled your component, you will have to create a corresponding pack file under the packs directory, which resides under the same level as the components directory. The configuration and instructions found in the pack file define several things for a component, including not limited to the following:
What services and other components it depends on
Default values for attributes
Monitor and threshold definitions
Custom payload details
Relationships such as
depends_on,managed_via, andsecured_via
A pack also defines the order of execution of components and is used to string components together to make them more effective and reusable.
Once a pack is defined it can be synced with the CMS using the included knife command or the OneOps CLI.
