Jira (PUP-4030) puppet module install does not consider no_proxy env var
Title: Message Title Chris Portman commented on PUP-4030 Re: puppet module install does not consider no_proxy env var Ive submitted a PR in an attempt to resolve this. In addition to accessing the forge, I also addressed it in other areas that I could find that considered the http_proxy variable when accessing the internet. https://github.com/puppetlabs/puppet/pull/3652 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 (FACT-233) Fact to add DHCP Server Details
Title: Message Title Chris Portman commented on an issue Re: Fact to add DHCP Server Details I've created PR https://github.com/puppetlabs/facter/pull/677 to handle nmcli = 0.9.9 Thanks, Chris Add Comment Facter / FACT-233 Fact to add DHCP Server Details Add per interface fact that shows the DHCP server IP for that interface if the interface IP is DHCP assigned. e.g. 'dhcp_server_eth0' Also add a 'dhcp_server' fact if the interface the machine uses to reach the default gateway is dhcp enabled. PR created: https://github.com/puppetlabs/facter/pull/559 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 (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Wouldn't this whole piece of functionality be subject to the outcomes of the conversation around
PUP-2086
?
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Ive updated the PR with tests that match the new behaviour.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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 (PUP-2098) 'only_uid' property on resources 'user'
Title: Message Title
Chris Portman created an issue
Puppet / PUP-2098
'only_uid' property on resources 'user'
Issue Type:
New Feature
Affects Versions:
3.x
Assignee:
Unassigned
Created:
30/Mar/14 4:00 PM
Priority:
Normal
Reporter:
Chris Portman
Add an 'only_uid' parameter to resources { 'user': }
to facilitate only purging within a specific selection of UIDs.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2086) Allow purging of groups with unless_system_group and unless_gid
Title: Message Title Chris Portman commented on an issue Re: Allow purging of groups with unless_system_group and unless_gid Sounds good. I do need to make a quick update to it (which im testing now). Thanks, Chris Add Comment Puppet / PUP-2086 Allow purging of groups with unless_system_group and unless_gid Implement parameters on the resources type similar to unless_system_user and unless_uid for groups (i.e unless_system_groups, unless_gid) 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 (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
I had an opportunity to test the PR overnight, and made a few updates to the commit. The above examples appear to work. The code does however create ranges from strings like '1..10' and then makes an array out of them. I'm not sure if this is the best way? But it seemed the most appropriate way to allow values that combine integers AND range like expressions such as '1, 5..10'
Any way, it works
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Nice, simple. Perhaps that should just be 'the way'. How big are the ranges you specify? Im wondering what the impact would be for ranges in the 1000's.
Im pretty keen to also implement this for groups as well. If this gets right, should just be a copy/paste (almost).
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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
Jira (PUP-2086) Allow purging of groups with unless_system_group and unless_gid
Title: Message Title Chris Portman created an issue Puppet / PUP-2086 Allow purging of groups with unless_system_group and unless_gid Issue Type: New Feature Assignee: Kylo Ginsberg Components: Types and Providers Created: 27/Mar/14 4:09 PM Priority: Normal Reporter: Chris Portman Implement parameters on the resources type similar to unless_system_user and unless_uid for groups (i.e unless_system_groups, unless_gid) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Hi Andy Parker,
I think it would greatly reduce the code complexity. And the code that I submitted basically just munges an array from the '1..4' syntax that looks like [ 1,2,3,4 ] anyway as opposed to an actual range object.
It would also be more consistent with the rest of the DSL (I think) in that I'm not aware of anywhere else you can use the '1..10' type syntax (expecting a range as a result)
Thanks, Chris
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
Andy Parker I updated the PR to only use values like:
1 '1' '1,2,3' [ 1, '2' ]
And the documentation for the parameter includes a Hint, directing users to the range function from stdlib.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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
Jira (PUP-2086) Allow purging of groups with unless_system_group and unless_gid
Title: Message Title Chris Portman commented on an issue Re: Allow purging of groups with unless_system_group and unless_gid I've added PR https://github.com/puppetlabs/puppet/pull/2484 to implement this Add Comment Puppet / PUP-2086 Allow purging of groups with unless_system_group and unless_gid Implement parameters on the resources type similar to unless_system_user and unless_uid for groups (i.e unless_system_groups, unless_gid) 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 (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
I wonder if it would also be useful to have a complimentary only_uid parameter. My use case will be to nominate a specific range of UIDs that I want completely under puppet control. Probably a range of about 1000 UIDs. Just thinking that it would be more efficient to specify a 1000 element array than array(s) containing All_UIDs - 1000
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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
Jira (PUP-2074) resourses type attribute unless_uid depends on unless_system_user
Title: Message Title Chris Portman created an issue Puppet / PUP-2074 resourses type attribute unless_uid depends on unless_system_user Issue Type: Bug Affects Versions: 3.x Assignee: Kylo Ginsberg Components: Types and Providers Created: 26/Mar/14 6:04 PM Priority: Normal Reporter: Chris Portman PUP-594 implemented 'unless_uid' as an attribute to resources however it looks as though its use is dependant on 'unless_system_user' being true. Add Comment
Jira (PUP-2074) resourses type attribute unless_uid depends on unless_system_user
Title: Message Title Chris Portman commented on an issue Re: resourses type attribute unless_uid depends on unless_system_user Created PR https://github.com/puppetlabs/puppet/pull/2478 Add Comment Puppet / PUP-2074 resourses type attribute unless_uid depends on unless_system_user PUP-594 implemented 'unless_uid' as an attribute to resources however it looks as though its use is dependant on 'unless_system_user' being true. 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 (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
I submitted PR https://github.com/puppetlabs/puppet/pull/2479 in an attempt to fix this. I dont have a 3.5.0 RC install to test with though, so im homping someone will be able to assist here.
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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 (PUP-2031) unless_uid on user is completely broken wrt ranges
Title: Message Title
Chris Portman commented on an issue
Re: unless_uid on user is completely broken wrt ranges
the PR should enable:
unless_uid = 1, unless_uid = '1,2', unless_uid = '3..5', unless_uid = '1,2,3..5', unless_uid = [1, '2', '3..5'],
Add Comment
Puppet / PUP-2031
unless_uid on user is completely broken wrt ranges
A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat} resources { 'user': purge = true, unless_system_user = true, unless_uid = 2, } {noformat} Broken: {noformat} resources { 'user': purge = true, ...
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 (PDB-523) Dedupe of exported resources
Title: Message Title Chris Portman created an issue PuppetDB / PDB-523 Dedupe of exported resources Issue Type: Bug Assignee: Unassigned Created: 24/Mar/14 2:39 PM Priority: Normal Reporter: Chris Portman Would it be possible to have PuppetDB dedupe exported resources, possibly on collection. They should still be stored per node so that they are reviewable on the API but when they are collected, it would be good if any IDENTICAL resources (name and attributes) could be consolidated. My use case for this is in scenarios where I have a load balancer (haproxy or apache) where i try to avoid having to pre-seed the load balancers with the service definitions and would rather have the balancer members export the service as well as the membership. Then the balancer would automatically add the service as well. However, this breaks as soon as there are 2 or more members exporting the same service definition. Add Comment
Jira (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Chris Portman commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Hi Andy Parker,
In your last comment on PR #184 (https://github.com/puppetlabs/hiera/pull/184), are you saying that % {%} {Something literal}
already works?
Thanks, Chris
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value http// I found out that during the lookup in the YAML backend, the answ...
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
Jira (FACT-233) Fact to add DHCP Server Details
Title: Message Title Chris Portman created an issue Facter / FACT-233 Fact to add DHCP Server Details Issue Type: Improvement Assignee: Chris Portman Created: 19/Jan/14 2:38 PM Environment: Linux Priority: Normal Reporter: Chris Portman Add per interface fact that shows the DHCP server IP for that interface if the interface IP is DHCP assigned. e.g. 'dhcp_server_eth0' Also add a 'dhcp_server' fact if the interface the machine uses to reach the default gateway is dhcp enabled. PR created: https://github.com/puppetlabs/facter/pull/559 Add Comment
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Chris Portman created an issue Facter / FACT-234 Add Facts showing the UUID of partitions Issue Type: Improvement Assignee: Chris Portman Created: 19/Jan/14 2:40 PM Environment: Linux Priority: Normal Reporter: Chris Portman Add facts 'blockdevice_dev_uuid' that show the partitions UUID. It ignores swap and iso9660 (CD/DVD devices). PR: https://github.com/puppetlabs/facter/pull/560 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
