Bug #20931: Using host_params in parameters leads to @Safemode doesn't allow to access 'host_params' on #<Safemode::ScopeObject>@ - Foreman

Bug #20931

Using host_params in parameters leads to @Safemode doesn't allow to access 'host_params' on #<Safemode::ScopeObject>@

Added by Ivan Necas 7 months ago. Updated 3 months ago.

Status:	Closed
Priority:	High
Assigned To:	Ivan Necas
Category:	Smart Variables
Target version:	Team Ivan Iteration 20
Difficulty:	medium	Bugzilla link:
Found in release:		Pull request:	https://github.com/theforeman/foreman/pull/4835

Story points	-
Velocity based estimate	-
Release	1.18.0	Release relationship	Auto

Description

1. use <%= host_params('blabla') %> inside the host parameters
2. Rendering fails on Safemode doesn't allow to access 'host_params' on #<Safemode::ScopeObject>

Related issues

Associated revisions

Revision 638d98a9
Added by Ivan Necas 3 months ago

Fixes #20931 - unify parameters and templates renderer (#4835)

Fixes #20931 - unify parameters and templates renderer

Before this patch, we used separate renderer for the parameters. This
caused issues when introducing more dsl methods for the templates that
we want to use in the parameters as well. Also, by the time of writing
the original SafeRenderer, there was no Renderer available.

After doing so, I was hitting issue with recursion, as
`Renderer.host_param` was using `@host.params` while the @host.params
was trying to render the params, that could include the `host_param`
call again, which lead to endless loop. After simplifying the
`HostParams` methods, it is possible to achieve this.

I also noticed that we were rendering only the inherited params and not
the non-inherited once. I've fixed this bug also as part of this patch.

Last but not least, due to the fact that we were using the
host_inherited_params for multiple purposes, we were rendering it also
when showing the host form, which was not even needed.