You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 15, 2024. It is now read-only.
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 text was updated successfully, but these errors were encountered:
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 text was updated successfully, but these errors were encountered: