Feature #1387
Class importer should support puppet dynamic environments
| Status: | Closed | Start: | 12/09/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | % Done: | 100% |
||
| Category: | Puppet | |||
| Target version: | 1.0 | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 0 |
Description
Hi
foreman should expand the $environment var from puppet. (for dynamic puppet environments)
rgds f0
Associated revisions
Revision 6c500f38497c873626e3c71e1149da8ac97e06ff
fixes #1387 - support puppet dynamic environments detection
Revision 0f2cfebb7a43ff34d994d8db0afc08adca0ae314
refs #1387 make sure that we won't fail if the modulepath detection is wrong
History
Updated by Florian Koch over 1 year ago
with this you can use $environment in the puppet conf for environments e.g
[master] modulepath=/etc/puppet/$environment/modules
Updated by Steve Traylen over 1 year ago
There's possibly good background to the benefit here:
http://puppetlabs.com/blog/git-workflow-and-puppet-environments/
Its way of adding new environments with out having to reconfigure the puppet master at all, i expect this is what Florian may want to acheive?
Updated by Florian Koch over 1 year ago
Steve Traylen wrote:
There's possibly good background to the benefit here:
http://puppetlabs.com/blog/git-workflow-and-puppet-environments/
Its way of adding new environments with out having to reconfigure the puppet master at all, i expect this is what Florian may want to acheive?
yes,exactly
Updated by Ohad Levy about 1 year ago
- Project changed from Foreman to Smart-Proxy
- Category deleted (
Puppet integration)
Updated by Ohad Levy about 1 year ago
- Subject changed from Foreman schould expand $environment to Class importer should support puppet dynamic environments
- Category set to Puppet
- Target version set to 1.0
Updated by Ohad Levy about 1 year ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 6c500f38497c873626e3c71e1149da8ac97e06ff.
