On Thu, Jan 26, 2017 at 11:16 AM, Timo Goebel <[email protected]> wrote: > How do you want to handle the "built"-Url? I think, you still need a > callback to Foreman when a Host has finished provisioning. That basically > voids most of the advantages (like improving reliability - btw: a Foreman ha > is easy vs. a smart-proxy ha setup is hard).
Yeah, sure, I noticed this too, but this built call is special - no output, no need of determining template API endpoint etc. It's a very simple case. > I do think, it's a good idea that Foreman knows the current state of an > installation. We could even show valueable information on the provisioning > progress or potential errors like with [2]. That would be a huge benefit for > users, at least from my experience. My proposal does not change that, I believe. Template contents audit is something I miss from the day one when I started with foreman and pre-rendering could basically help with that - we could put whole template content into audit record during build, so we can be sure clients see the exactly same. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
