Actions
Feature #16740
closedHost parameters should be available in templates using some macro
Difficulty:
Triaged:
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).
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3983 added
Updated by Ondřej Pražák over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Updated by The Foreman Bot about 8 years ago
- Pull request https://github.com/theforeman/community-templates/pull/343 added
Updated by The Foreman Bot about 8 years ago
- Pull request https://github.com/theforeman/foreman/pull/4187 added
Updated by Ivan Necas over 7 years ago
- Related to Bug #20931: Using host_params in parameters leads to @Safemode doesn't allow to access 'host_params' on #<Safemode::ScopeObject>@ added
Updated by Ivan Necas over 7 years ago
- Related to Bug #20968: invalid YAML in lookup keys can break db migrations added
Updated by Marek Hulán about 7 years ago
- Related to Bug #22483: SSH key setup does not work added
Updated by Lukas Zapletal almost 7 years ago
- Related to Bug #23934: Still some @host.param leftovers added
Updated by Tomer Brisker over 6 years ago
- Related to Bug #24640: 1.17 migration causes array/hash values for parameters to turn into strings with escaped quotes added
Actions