Feature #16740
closed
Host parameters should be available in templates using some macro
Added by Marek Hulán about 8 years ago.
Updated over 6 years ago.
Description
We should provide easy way to use all host parameters in templates to avoid calling internal method like @host.info['parameter'] or variable @parameters. Also there should be only one way so users don't have to check both info and @parameters. Ideally we'd add some macro to access it, which would also cache it while keeping it lazy (load on first time access).
- Description updated (diff)
- Target version changed from 115 to 1.5.0
- Target version changed from 1.5.0 to 1.4.2
- Assignee set to Ondřej Pražák
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3983 added
- Target version changed from 1.4.2 to 1.4.4
- Target version changed from 1.4.4 to 1.10.1
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 209
- Pull request https://github.com/theforeman/community-templates/pull/343 added
- Pull request https://github.com/theforeman/foreman/pull/4187 added
- Target version changed from 1.10.1 to 1.17.0-RC2
- Related to Bug #20931: Using host_params in parameters leads to @Safemode doesn't allow to access 'host_params' on #<Safemode::ScopeObject>@ added
- Related to Bug #20968: invalid YAML in lookup keys can break db migrations added
- Related to Bug #22483: SSH key setup does not work added
- Related to Bug #23934: Still some @host.param leftovers added
- Related to Bug #24640: 1.17 migration causes array/hash values for parameters to turn into strings with escaped quotes added
Also available in: Atom
PDF