Actions
Feature #8142
closed
As a user I would like remote command scripts to leverage smart variables
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
Foreman provides a general purpose smart variable facility to inform kickstarts, snippets, and puppet modules. This user story expresses the desire to extend the concept of smart variables to remote-execution scripting. Examples of smart variables might include the FQHN of the target system, the environment, the location, the presence or absence of a given FACT.
Updated by David Caplan over 9 years ago
- Blocks Tracker #8121: Remote Execution Tracker added
Updated by Dominic Cleal almost 8 years ago
- Project changed from Foreman to Foreman Remote Execution
- Category deleted (
Parameters)
Updated by Marek Hulán almost 8 years ago
we are only missing the environment and the location as template inputs but it can be easily obtained via @host.location and @host.environment. We should formalize this on input level, possibly also os. Or introduce new macros for this.
Updated by Marek Hulán almost 8 years ago
- Related to Feature #15371: Provide OS detection macros for (job) templates added
Updated by Marek Hulán almost 8 years ago
- Blocks deleted (Tracker #8121: Remote Execution Tracker)
Updated by Marek Hulán about 3 years ago
- Status changed from New to Rejected
environments is being extracted, locations should be done as a separate template input allowing any resources loading
Actions