The paradigm you wish users to adhere to for programatic generation of a flapjack_config.yaml file should be documented.
Is your idea that the file will be pre-rendered, and just laid down via puppet? or is it your vision that some bits of content contained in the file would be consumed via parameters to the puppet module, and the flapjack_config.yaml generated dynamically?
The paradigm you wish users to adhere to for programatic generation of a flapjack_config.yaml file should be documented.
Is your idea that the file will be pre-rendered, and just laid down via puppet? or is it your vision that some bits of content contained in the file would be consumed via parameters to the puppet module, and the flapjack_config.yaml generated dynamically?