Skip to content
This repository has been archived by the owner on May 15, 2024. It is now read-only.

flapjack_config.yaml generation process undocumented #2

Open
wolfspyre opened this issue Oct 6, 2014 · 1 comment
Open

flapjack_config.yaml generation process undocumented #2

wolfspyre opened this issue Oct 6, 2014 · 1 comment

Comments

@wolfspyre
Copy link
Contributor

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?

@Sarah-E-Greene
Copy link

/cc @jessereynolds @ali-graham

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants