Jira (HI-522) deeper merge not being respected
Title: Message Title Kyle Decot commented on HI-522 Re: deeper merge not being respected Thanks for the response Henrik Lindberg. Turns out that you're right and that I should have been using hiera_hash instead of the regular hiera call. Thanks again Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title
Kyle Decot updated an issue
Hiera / HI-522
deeper merge not being respected
Change By:
Kyle Decot
When performing `puppet agent -t` on my node I am not receiving the hiera values that I expect. I have specified the deeper merge strategy as::hierarchy: - "%{::fqdn}" - common:merge_behavior: deeper:deep_merge_options: :knockout_prefix: '--'I have also installed the gem using:puppetserver gem install deep_mergeIn common.yaml I have something like:foo: - bar: "hello" - baz: "world"and then in my node's yaml file I havefoo: - "hello"When performing a run w/ hiera("foo", {}) I'm only getting a single item when I would expect two
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title
Kyle Decot updated an issue
Hiera / HI-522
deeper merge not being respected
Change By:
Kyle Decot
When performing `puppet agent -t` on my node I am not receiving the hiera values that I expect. I have specified the deeper merge strategy as: :hierarchy: - "%{::fqdn}" - common:merge_behavior: deeper:deep_merge_options: :knockout_prefix: '--'I have also installed the gem using:puppetserver gem install deep_mergeIn common.yaml I have something like:foo: - bar: "hello" - baz: "world"and then in my node's yaml file I havefoo: "hello"When performing a run w/ hiera("foo", {}) I'm only getting a single item when I would expect two
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title
Kyle Decot created an issue
Hiera / HI-522
deeper merge not being respected
Issue Type:
Bug
Affects Versions:
HI 3.1.1
Assignee:
Unassigned
Components:
Community
Created:
2016/07/05 12:03 PM
Priority:
Normal
Reporter:
Kyle Decot
When performing `puppet agent -t` on my node I am not receiving the hiera values that I expect. I have specified the deeper merge strategy as:
:hierarchy:
"%{::fqdn}"
common :merge_behavior: deeper :deep_merge_options: :knockout_prefix: '--'
I have also installed the gem using:
puppetserver gem install deep_merge
In common.yaml I have something like:
foo:
Jira (PUP-6265) puppetlabs-splunk --accept-license --answer-yes
Title: Message Title Kyle Decot assigned an issue to Hunter Haugen Puppet / PUP-6265 puppetlabs-splunk --accept-license --answer-yes Change By: Kyle Decot Assignee: Hunter Haugen Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6265) puppetlabs-splunk --accept-license --answer-yes
Title: Message Title Kyle Decot created an issue Puppet / PUP-6265 puppetlabs-splunk --accept-license --answer-yes Issue Type: Bug Assignee: Unassigned Created: 2016/05/04 1:49 PM Priority: Normal Reporter: Kyle Decot Using the puppetlabs-splunk module to upgrade the splunk forwarder is currently not possible because starting the service will fail due to the license not being accepted and the upgrade not being agreed to. The service need to accept the following flags: --accept-license --answer-yes Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6263) puppetlabs-splunk doesn't update
Title: Message Title Kyle Decot assigned an issue to Hunter Haugen Puppet / PUP-6263 puppetlabs-splunk doesn't update Change By: Kyle Decot Assignee: Hunter Haugen Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6263) puppetlabs-splunk doesn't update
Title: Message Title Kyle Decot updated an issue Puppet / PUP-6263 puppetlabs-splunk doesn't update Change By: Kyle Decot Attachment: splunk.pp Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6263) puppetlabs-splunk doesn't update
Title: Message Title
Kyle Decot updated an issue
Puppet / PUP-6263
puppetlabs-splunk doesn't update
Change By:
Kyle Decot
When attempting to use the official puppetlabs splunk module (v.4.0.0) updating the version/build in the params does not seem to update the splunk forwarder. The first time the module runs the forwarder will be installed w/ the version/build specified but attempting to upgrade after that has no effect.class profiles::splunk { class { 'splunk::params':version => '6.4.0',build => 'f2c836328108',src_root => 'puppet:///public/splunk', } class { 'splunk::forwarder': }} I will note however that when increasing the build/version and doing a run I get something like:Notice: /Stage[main]/Splunk::Forwarder/Staging::File[splunkforwarder-6.4.0-f2c836328108-linux-2.6-x86_64.rpm]/File[/opt/staging/splunk/splunkforwarder-6.4.0-f2c836328108-linux-2.6-x86_64.rpm]/ensure: defined content as '{md5}7d06f0343d0c210445c0e497b9c6806c'The file however seems to remain in /opt/staging and never get moved to it's final location.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6263) puppetlabs-splunk doesn't update
Title: Message Title
Kyle Decot updated an issue
Puppet / PUP-6263
puppetlabs-splunk doesn't update
Change By:
Kyle Decot
When attempting to use the official puppetlabs splunk module updating the version/build in the params does not seem to update the splunk forwarder. The first time the module runs the forwarder will be installed w/ the version/build specified but attempting to upgrade after that has no effect. {{ class profiles::splunk { class { 'splunk::params':version => '6.4.0',build => 'f2c836328108',src_root => 'puppet:///public/splunk', } class { 'splunk::forwarder': }} }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6263) puppetlabs-splunk doesn't update
Title: Message Title
Kyle Decot updated an issue
Puppet / PUP-6263
puppetlabs-splunk doesn't update
Change By:
Kyle Decot
When attempting to use the official puppetlabs splunk module updating the version/build in the params does not seem to update the splunk forwarder. The first time the module runs the forwarder will be installed w/ the version/build specified but attempting to upgrade after that has no effect. {{ class profiles::splunk { class { 'splunk::params':version => '6.4.0',build => 'f2c836328108',src_root => 'puppet:///public/splunk', } class { 'splunk::forwarder': }} }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6263) puppetlabs-splunk doesn't update
Title: Message Title
Kyle Decot created an issue
Puppet / PUP-6263
puppetlabs-splunk doesn't update
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/05/04 1:15 PM
Priority:
Normal
Reporter:
Kyle Decot
When attempting to use the official puppetlabs splunk module updating the version/build in the params does not seem to update the splunk forwarder. The first time the module runs the forwarder will be installed w/ the version/build specified but attempting to upgrade after that has no effect.
class profiles::splunk { class { 'splunk::params': version => '6.4.0', build => 'f2c836328108', src_root => 'puppet:///public/splunk', }
class { 'splunk::forwarder': }
}
Add Comment
Jira (PUP-5298) file function doesn't support serving of files from mount point
Title: Message Title
Kyle Decot created an issue
Puppet / PUP-5298
file function doesn't support serving of files from mount point
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/09/30 8:05 AM
Priority:
Major
Reporter:
Kyle Decot
When using the file function you are currently unable to do something like:
file("puppet://mount_point/some_file")
This will always insist that the file doesn't exist
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-4901) puppet-splunk doesn't update spunk
Title: Message Title Kyle Decot assigned an issue to Hunter Haugen Puppet / PUP-4901 puppet-splunk doesn't update spunk Change By: Kyle Decot Assignee: Hunter Haugen Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 (PUP-4901) puppet-splunk doesn't update spunk
Title: Message Title Kyle Decot updated an issue Puppet / PUP-4901 puppet-splunk doesn't update spunk Change By: Kyle Decot Priority: Normal Major 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 (PUP-4901) puppet-splunk doesn't update spunk
Title: Message Title Kyle Decot created an issue Puppet / PUP-4901 puppet-splunk doesn't update spunk Issue Type: Bug Assignee: Unassigned Created: 2015/07/20 6:08 AM Priority: Normal Reporter: Kyle Decot When using the official splunk module it installs perfectly the first time. However when updating the version numbers and rerunning puppet the package doesn't actually get updated. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
