Jira (PUP-5612) Error message for declaring resource without title is confusing
Title: Message Title
Kjetil Torgrim Homme commented on PUP-5612
Re: Error message for declaring resource without title is confusing
Since searching for this error message on the web has this issue as the top hit: This error message will still appear for resource references with whitespace between the resource type and name. ``` class acme::install { notice("install") } class acme { class \{ 'acme::install': } -> Class [ 'acme' ] } include acme ``` > Error: Could not parse for environment production: This Array _expression_ has no effect. A Host Class Definition can not end with a value-producing _expression_ without other effect (file: /tmp/init.pp, line: 7, column: 9) Removing the space so it becomes `Class[ 'acme' ]` solves the issue. I'm not suggesting re-opening the issue or see a big need to fix this
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.109557.145017207.62445.1669888680289%40Atlassian.JIRA.
Jira (PUP-1583) Non ASCII comments in puppet.conf causes exception
Title: Message Title Kjetil Torgrim Homme commented on PUP-1583 Re: Non ASCII comments in puppet.conf causes exception on Ubuntu and Debian, SysV and Upstart will not initialise locale environment variables for services. each init script will need to do . /etc/default/locale I don't think it is a good idea to require systems to duplicate these settings into /etc/default/puppet or similar. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-282) hiera binary with `-i nodename.domain.com` fails under puppet 3
Title: Message Title Kjetil Torgrim Homme commented on HI-282 Re: hiera binary with `-i nodename.domain.com` fails under puppet 3 the original patch + changing terminus_class to :puppetdb instead of :rest works for me. perhaps it would be better to make a new option since this is a different API than the inventory service. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-225) allow interleaved querying of backends
Title: Message Title
Kjetil Torgrim Homme commented on an issue
Re: allow interleaved querying of backends
no, of course not. current behaviour will remain the default.
Add Comment
Hiera / HI-225
allow interleaved querying of backends
When Hiera processes the sources, it will iterate through them completely, first with the first backend, then the next backend. Given a hiera.yaml like :hierarchy: - site-%{::site} - common :backends: - yaml - json and the files site-external.json and common.yaml, the value in common.yaml will override the value in site-e...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-225) allow interleaved querying of backends
Title: Message Title
Kjetil Torgrim Homme created an issue
Hiera / HI-225
allow interleaved querying of backends
Issue Type:
New Feature
Assignee:
Adrien Thebo
Components:
Community
Created:
18/Mar/14 9:13 AM
Environment:
any
Priority:
Normal
Reporter:
Kjetil Torgrim Homme
Original Estimate:
4 hours
Remaining Estimate:
1 hour
When Hiera processes the sources, it will iterate through them completely, first with the first backend, then the next backend.
Given a hiera.yaml like
:hierarchy:
site-%{::site}
Jira (HI-225) allow interleaved querying of backends
Title: Message Title
Kjetil Torgrim Homme commented on an issue
Re: allow interleaved querying of backends
as indicated by Time Tracking, I have a patch ready, but I haven't updated the rspec tests yet. will add pull request when tests pass again
Add Comment
Hiera / HI-225
allow interleaved querying of backends
When Hiera processes the sources, it will iterate through them completely, first with the first backend, then the next backend. Given a hiera.yaml like :hierarchy: - site-%{::site} - common :backends: - yaml - json and the files site-external.json and common.yaml, the value in common.yaml will override the value in site-e...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
