Re: [foreman-dev] RFC idea: Templates rendering only through Proxies

On Fri, Jan 27, 2017 at 12:23 AM, Greg Sutcliffe wrote: > I'll comment on the rest of this when I have time to think it over, > however I > do want to correct one point: > > On Thursday, 26 January 2017 10:27:47 CET Lukas Zapletal wrote: > > > This is only relevant to

Re: [foreman-dev] RFC idea: Templates rendering only through Proxies

I'll comment on the rest of this when I have time to think it over, however I do want to correct one point: On Thursday, 26 January 2017 10:27:47 CET Lukas Zapletal wrote: > This is only relevant to provision, iPXE and script templates, all the > others are not affected by this. PXE templates

Re: [foreman-dev] RFC idea: Templates rendering only through Proxies

I think this is a good idea; and it can be pushed into separating templates into a standalone service which would handle the whole template lifecycle, not just serving of pre-rendered templates (if eventually). Also agreed re: “built” ping, it’s a special call, although the responsibility for

Re: [foreman-dev] RFC idea: Templates rendering only through Proxies

Hi, > our design of template proxying is not good I don't think, it's that bad. Your suggestion does have it's advantages, though. From a security perspective it would be great if the smart-proxy wouldn't need any calls to Foreman. > The downside is that Smart Proxy would be required in

[foreman-dev] RFC idea: Templates rendering only through Proxies

Hey, our design of template proxying is not good, I constantly need to solve problems setting it up. In order to have this working, both Templates and TFTP features needs to be turned on. This is confusing, then several Proxy settings need to be correctly set and since the names are also