Bug #1991
LDAP and using puppetVar variables in Puppet
| Status: | Closed | Start date: | 02/18/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | LDAP | |||
| Target version: | 0.24.8 | |||
| Affected Puppet version: | 0.24.7 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
when using puppetVar variables within puppet all are automatically converted to string, including true and false. So what was once working with internal nodes:
case $config_da_clamd {
false: { include directadmin-clamd::remove }
default: { include directadmin-clamd::install }
}
Must now be:
case $config_da_clamd {
"false": { include directadmin-clamd::remove }
default: { include directadmin-clamd::install }
}
When using LDAP.
As a work around use the get_var in the wiki to ensure true and false are booleans.
http://reductivelabs.com/trac/puppet/wiki/LDAPNodes
History
Updated by James Turnbull almost 3 years ago
- Category set to LDAP
- Status changed from Unreviewed to Accepted
- Assignee set to Luke Kanies
- Target version set to 0.24.8
Updated by Luke Kanies almost 3 years ago
- Status changed from Accepted to In Topic Branch Pending Review
- Assignee changed from Luke Kanies to Lawrence Ludwig
Fixed in the tickets/0.24.x/1991 branch in my repo; please verify it does what you expect.
Updated by Lawrence Ludwig almost 3 years ago
- Status changed from In Topic Branch Pending Review to Ready For Checkin
- Assignee changed from Lawrence Ludwig to James Turnbull
From testing it appears to do the trick.
Updated by James Turnbull almost 3 years ago
- Status changed from Ready For Checkin to Closed
Pushed in commit:61661b1c46fafeabf1bdbc4778762831d7178d91 in branch 0.24.x