Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like{code:yaml}hierarchy: - name: "Node-specific Hiera data, via trusted and via fact" lookup_key data_hash : getvarpaths: - "trusted.external.servicenow.hieradata" - "trusted.external.unicorn.hieradata" - "facts.hieradata" - name: "Some yaml stuff"data_hash: yamlpaths: - "environments/%{trusted.extensions.pp_environment}.yaml" - "common.yaml"{code}where for the {{getvar}} Hiera layer, {{path}} (or each entry in {{paths}}) resolves to a {{Hash}} value containing hiera lookup keys. For example:{code:json}{ "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"}{code}To provide best-practices guardrails, by default {{path}} must start with a valid top-scope variable such as {{trusted}} or {{facts}}, because per Hiera best practices, only variables not subject to evaluation-order dependencies or calling scope should be referenced in hiera.yaml. Thus, the following hierarchy configuration should fail:{code:yaml}---hierarchy: - name: "Example failure" lookup_key data_hash : getvarpath: "class_scope_variable.hieradata"{code}The error emitted should look something like:{panel}{{ERROR: /etc/puppetlabs/code/environments/production/hiera.yaml: getvar hierarchy level "Example failure" is configured to consult missing or non-topscope variable "class_scope_variable". This is prohibited by the topscope_variables_only=true option, which dictates that variables consulted must exist and be in topscope. If you would like to consult "class_scope_variable" anyway, you must set topscope_variables_only=false.}} {panel}Configuring the backend to allow the use of non-topscope variables would look like this:{code:yaml}---hierarchy: - name: "Example failure (bypassed)" lookup_key data_hash : getvarpath: "class_scope_variable.hieradata"options: topscope_variables_only: false{code} The backend type should be {{data_hash}}. The most technically appropriate type might be {{lookup_key}}, but there are UX considerations here and the name {{data_hash}} helps communicate to the user how this works—the data returned should be like what you find in a yaml file, which is type {{data_hash}}.
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like {code:yaml} hierarchy: - name: "Node-specific Hiera data, via trusted and via fact"lookup_key: getvarpaths: - "trusted.external.servicenow.hieradata" - "trusted.external.unicorn.hieradata" - "facts.hieradata" - name: "Some yaml stuff"data_hash: yamlpaths: - "environments/%{trusted.extensions.pp_environment}.yaml" - "common.yaml"{code} where for the {{getvar}} Hiera layer, {{path}} (or each entry in {{paths}}) resolves to a {{Hash}} value containing hiera lookup keys. For example: {code:json}{ "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"}{code} To provide best-practices guardrails, by default {{path}} must start with a valid top-scope variable such as {{trusted}} or {{facts}}, because per Hiera best practices, only variables not subject to evaluation-order dependencies or calling scope should be referenced in hiera.yaml. Thus, the following hierarchy configuration should fail: {code:yaml} ---hierarchy: - name: "Example failure"lookup_key: getvarpath: "class_scope_variable.hieradata"{code} The error emitted should look something like: { code panel } {{ ERROR: /etc/puppetlabs/code/environments/production/hiera.yaml : getvar hierarchy level "Example failure" is configured to consult missing or non-topscope variable "class_scope_variable". This is prohibited by the topscope_variables_only=true option, which dictates that variables consulted must exist and be in topscope. If you would like to consult "class_scope_variable" anyway, you must set topscope_variables_only=false. }} { code panel } Configuring the backend to allow the use of non-topscope variables would look like this: {code:yaml} ---hierarchy: - name: "Example failure (bypassed)"lookup_key: getvarpath: "class_scope_variable.hieradata"options: topscope_variables_only: false{code}
Add
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like{code:yaml}hierarchy: - name: "Node-specific Hiera data, via trusted and via fact"lookup_key: getvarpaths: - "trusted.external.servicenow.hieradata" - "trusted.external.unicorn.hieradata" - "facts.hieradata" - name: "Some yaml stuff"data_hash: yamlpaths: - "environments/%{trusted.extensions.pp_environment}.yaml" - "common.yaml"{code}where for the {{getvar}} Hiera layer, {{path}} (or each entry in {{paths}}) resolves to a {{Hash}} value containing hiera lookup keys. For example:{code:json}{ "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"}{code}To provide best-practices guardrails, by default {{path}} must start with a valid top-scope variable such as {{trusted}} or {{facts}}, because per Hiera best practices, only variables not subject to evaluation-order dependencies or calling scope should be referenced in hiera.yaml. Thus, the following hierarchy configuration should fail:{code:yaml}---hierarchy: - name: "Example failure"lookup_key: getvarpath: "class_scope_variable.hieradata"{code}The error emitted should look something like:{code}ERROR: /etc/puppetlabs/code/environments/production/hiera.yaml getvar hierarchy level "Example failure" is configured to consult missing or non-topscope variable "class_scope_variable". This is prohibited by the topscope_variables_only=true option, which dictates that variables consulted must exist and be in topscope. If you would like to consult "class_scope_variable" anyway, you must set topscope_variables_only=false.{code}Configuring the backend to allow the use of non-topscope variables would look like this:{code:yaml}---hierarchy: - name: "Example failure (bypassed) "lookup_key: getvarpath: "class_scope_variable.hieradata"options: topscope_variables_only: false{code}
Add Comment
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like {code:yaml} --- hierarchy: - name: " ServiceNow hiera Node-specific Hiera data , via trusted and via fact "lookup_key: getvar path paths : - " trusted.external.servicenow. hiera_data hieradata" - "trusted.external.unicorn.hieradata" - "facts.hieradata" - name: " User fact Hiera data Some yaml stuff " lookup_key data_hash : getvar yaml path paths : facts - "environments/%{trusted . hiera extensions . data pp_environment}.yaml" - "common.yaml" {code} where for the {{ getvar}} Hiera layer, {{ path}} (or each entry in {{paths}}) resolves to a {{Hash}} value containing hiera lookup keys , e . g. For example: {code:json}{ "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"} {code} To provide best-practices guardrails, by default {{path}} must start with a valid top-scope variable such as {{trusted}} or {{facts}} since those are the top-level , because per Hiera best practices, only variables that we've deemed safe not subject to use evaluation-order dependencies or calling scope should be referenced in hiera . All other paths will raise an error yaml . Thus, the following hierarchy configuration should fail: People who want to use other, unsafe top {code:yaml} - level variables can do so via an --hierarchy: - name: "Example failure"lookup_key: getvarpath: "class_scope_variable.hieradata" { code}The error emitted should look something like: { unsafe code } } ERROR: /etc/puppetlabs/code/environments/production/hiera.yaml getvar hierarchy level "Example failure" is configured to consult missing or non-topscope variable "class_scope_variable". This is prohibited by the topscope_variables_only=true option , which dictates that variables consulted must exist and be in topscope . If you would like to consult "class_scope_variable" anyway, you must set topscope_variables_only=false.{code} Configuring that the backend to allow the use of non-topscope variables would look something like this: {code :yaml } - --hierarchy: - name: " unsafe hiera data Example failure " lookup_key: getvar path: foo "class_scope_variable . bar hieradata" unsafe options : true topscope_variables_only: false {code}
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like{code:yaml}---hierarchy: - name: "ServiceNow hiera data"lookup_key: getvarpath: trusted.external.servicenow.hiera_data - name: "User fact Hiera data" lookup_key: getvar path: facts.hiera.data{code}where {{path}} (or each entry in {{paths}}) resolves to a {{Hash}} value containing hiera lookup keys, e.g.{code:json}{ "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"} {code} {{path}} must start with {{trusted}} or {{facts}} since those are the top-level variables that we've deemed safe to use. All other paths will raise an error.People who want to use other, unsafe top-level variables can do so via an {{unsafe}} option. Configuring that would look something like{code}- name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like{code :yaml } --- hierarchy: - name: "ServiceNow hiera data"lookup_key: getvarpath: trusted.external.servicenow.hiera_data - name: "User fact Hiera data"lookup_key: getvarpath: facts.hiera.data {code}where {{path}} (or each entry in {{paths}}) resolves to a {{Hash}} value containing hiera lookup keys, e.g.{code: java json }{ "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"} {code} {{path}} must start with {{trusted}} or {{facts}} since those are the top-level variables that we've deemed safe to use. All other paths will raise an error.People who want to use other, unsafe top-level variables can do so via an {{unsafe}} option. Configuring that would look something like{code}- name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like{code}- --hierarchy: - name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data - name: "User fact Hiera data"lookup_key: getvarpath: facts.hiera.data {code}where {{path}} (or each entry in {{paths}}) resolves to a {{Hash}} value containing hiera lookup keys, e.g.{code:java} { "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"} {code} {{path}} must start with {{trusted}} or {{facts}} since those are the top-level variables that we've deemed safe to use. All other paths will raise an error.People who want to use other, unsafe top-level variables can do so via an {{unsafe}} option. Configuring that would look something like{code}- name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Reid Vandewiele
Configuring this would look something like {code} - name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code} where {{path}} (or each entry in {{paths}}) resolves to a {{Hash}} value whose key you're looking up containing hiera lookup keys, e . g. { code:java} { "cygwin::enable": false, "ntp::servers": ["time.nist.gov","clock.sjc.he.net" ], "ntp::restrict": ["127.0.0.1" ], "ntp::disable_monitor": true, "resource_api::agent::api_version": "1.4.2", "resource_api::server::api_version": "1.4.2", "syslog::server": "rsyslog.ops.puppetlabs.net"} {code} {{ path}} must start with {{trusted}} or {{facts}} since those are the top-level variables that we've deemed safe to use. All other paths will raise an error.People who want to use other, unsafe top-level variables can do so via an {{unsafe}} option. Configuring that would look something like {code} - name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4654 Adjust PDB config to allow for multiple write dbs Change By: Rob Browning Story Points: 2 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347165.1582246233000.51335.1588198140031%40Atlassian.JIRA.
Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4654 Adjust PDB config to allow for multiple write dbs Change By: Rob Browning Sprint: HA Team (Ready For Work) 2020-05-05 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347165.1582246233000.51334.1588198080674%40Atlassian.JIRA.
Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4654 Adjust PDB config to allow for multiple write dbs Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347165.1582246233000.51317.1588198020025%40Atlassian.JIRA.
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title Rob Braden updated an issue Puppet / PUP-10478 Add getvar Hiera backend Change By: Rob Braden Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357322.1588196554000.51301.1588197720137%40Atlassian.JIRA.
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title Enis Inan updated an issue Puppet / PUP-10478 Add getvar Hiera backend Change By: Enis Inan Epic Link: PIE-241 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357322.1588196554000.51244.158819790%40Atlassian.JIRA.
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Enis Inan
Configuring this would look something like{code}- name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code}where {{path}} resolves to a {{Hash}} value whose key you're looking up. The allowable paths are {{ trusted.* path }} and must start with {{ facts.*}} (so the {{ trusted}} or {{facts}} hashes or anything in since those hashes) are the top-level variables that we've deemed safe to use . All other paths will raise an error. This is People who want to prevent people from using ( use other, unsafe ) top- scope level variables to get Hiera data (bad practice). However, we will still support unsafe access can do so via an {{unsafe}} option. Configuring that would look something like{code}- name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-9469) Remove the setting to turn off func 3x API validation
Title: Message Title Justin Stoller commented on PUP-9469 Re: Remove the setting to turn off func 3x API validation Yes, we should add a deprecation notice for users who set the func3x_check setting to false. It currently defaults to true. There is one conditional in code that honors this setting it should be trivial to remove. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.294057.1548939109000.51223.1588196760020%40Atlassian.JIRA.
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Enis Inan
Configuring this would look something like{code}- name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code}where {{path}} resolves to a {{Hash}} value whose key you're looking up. The allowable paths are {{trusted.*}} and {{facts.*}} (so anything in the {{trusted}} or {{facts}} hash hashes or anything in those hashes ). All other paths will raise an error. This is to prevent people from using (unsafe) top-scope variables to get Hiera data (bad practice). However, we will still support unsafe access via an {{unsafe}} option. Configuring that would look something like{code}- name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Enis Inan
Configuring this would look something like{code}- name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code}where {{path}} resolves to a {{Hash}} value whose key you're looking up. The allowable {{path}}s are {{trusted.*}} and {{facts.*}} (so anything in the {{trusted}} or {{facts}} hash). All other paths will raise an error. This is to prevent people from using (unsafe) top-scope variables to get Hiera data (bad practice). However, we will still support unsafe access via an {{unsafe}} option. Configuring that would look something like{code} - name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Enis Inan
Configuring this would look something like{code}- name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code}where {{path}} resolves to a {{Hash}} value whose key you're looking up. The allowable {{path}}s paths are {{trusted.*}} and {{facts.*}} (so anything in the {{trusted}} or {{facts}} hash). All other paths will raise an error. This is to prevent people from using (unsafe) top-scope variables to get Hiera data (bad practice). However, we will still support unsafe access via an {{unsafe}} option. Configuring that would look something like{code}- name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Enis Inan
Configuring this would look something like{code}- name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code}where {{path}} resolves to a {{Hash}} value whose key you're looking up. The allowable {{path}}s are {{trusted.*}} and {{facts.*}} (so anything in the {{trusted}} or {{facts}} hash). All other paths will raise an error. This is to prevent people from using (unsafe) top-scope variables to get Hiera data (bad practice). However, we will still support unsafe access via an {{unsafe}} option. Configuring that would look something like{code} - name: "unsafe hiera data"lookup_key: getvarpath: foo.barunsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Enis Inan
Configuring this would look something like{code} - name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code}where {{path}} resolves to a {{Hash}} value whose key you're looking up. The allowable {{path}}s are {{trusted.*}} and {{facts.*}} (so anything in the {{trusted}} or {{facts}} hash). All other paths will raise an error. This is to prevent people from using (unsafe) top-scope variables to get Hiera data (bad practice). However, we will still support unsafe access via an {{unsafe}} option. Configuring that would look something like ``` {code} - name: "unsafe hiera data"lookup_key: getvarpath: foo.barunsafe: true ``` {code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-10478
Add getvar Hiera backend
Change By:
Enis Inan
Configuring this would look something like{code}- name: "ServiceNow hiera data" lookup_key: getvar path: trusted.external.servicenow.hiera_data{code}where {{path}} resolves to a {{Hash}} value whose key you're looking up. The allowable {{path}}s are {{trusted.*}} and {{facts.*}} (so anything in the {{trusted}} or {{facts}} hash). All other paths will raise an error. This is to prevent people from using (unsafe) top-scope variables to get Hiera data (bad practice). However, we will still support unsafe access via an {{unsafe}} option. Configuring that would look something like{code} - name: "unsafe hiera data"lookup_key: getvarpath: foo.barunsafe: true{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving
Jira (PUP-10478) Add getvar lookup-key Hiera backend
Title: Message Title
Enis Inan created an issue
Puppet / PUP-10478
Add getvar lookup-key Hiera backend
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/04/29 2:42 PM
Fix Versions:
PUP 6.15.0
Priority:
Normal
Reporter:
Enis Inan
Configuring this would look something like
- name: "ServiceNow hiera data"
lookup_key: getvar
path: trusted.external.servicenow.hiera_data
where path resolves to a Hash value whose key you're looking up. The allowable path}}s are {{trusted. and facts. (so anything in the trusted or facts hash). All other paths will raise an error. This is to prevent people from using (unsafe) top-scope variables to get Hiera data (bad practice). However, we will still support unsafe access via an unsafe option. Configuring that would look something like ```
name: "unsafe hiera data" lookup_key: getvar path: foo.bar unsafe: true ```
Jira (PUP-10478) Add getvar Hiera backend
Title: Message Title Enis Inan updated an issue Puppet / PUP-10478 Add getvar Hiera backend Change By: Enis Inan Summary: Add getvar lookup-key Hiera backend Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357322.1588196554000.51215.1588196581000%40Atlassian.JIRA.
Jira (PUP-9696) Cannot use URIs that require escaping after interpolation
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9696 Cannot use URIs that require escaping after interpolation Change By: Melissa Stone Team: Froyo Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.301445.155353411.51171.1588196160081%40Atlassian.JIRA.
Jira (PUP-9696) Cannot use URIs that require escaping after interpolation
Title: Message Title Melissa Stone commented on PUP-9696 Re: Cannot use URIs that require escaping after interpolation Probably some places we should be escaping but we aren't (ie forge) URI.escape is deprecated in Ruby itself. Everyone either needs to use the Puppet URI escape/unescape logic in Puppet::Util, or we need to add something like addressable and using that everywhere. We might not want to expose that as the way to do it, but since this is in Heira, that should be okay. What we should do is use the escape/unescape logic in Puppet::Util everywhere in puppet, and use addressable under the hood there. Then in hiera, we can just straight use addressable because that's in hiera. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.301445.155353411.51170.1588196160076%40Atlassian.JIRA.
Jira (PUP-9696) Cannot use URIs that require escaping after interpolation
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9696 Cannot use URIs that require escaping after interpolation Change By: Melissa Stone Sub-team: Language Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.301445.155353411.51169.1588196160071%40Atlassian.JIRA.
Jira (PUP-9690) Remove deprecated Puppet::Agent::Locker#running? method
Title: Message Title Melissa Stone commented on PUP-9690 Re: Remove deprecated Puppet::Agent::Locker#running? method We need to either fix the code or remove the deprecation warning. Since Night's Watch already has several locking tickets that they are looking at, I'm going to assign it to that team. cc/ Mihai Buzgau Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.307358.1556917277000.51131.1588195440130%40Atlassian.JIRA.
Jira (PUP-9690) Remove deprecated Puppet::Agent::Locker#running? method
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9690 Remove deprecated Puppet::Agent::Locker#running? method Change By: Melissa Stone Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.307358.1556917277000.51132.1588195440175%40Atlassian.JIRA.
Jira (PUP-9648) Drop PSON support
Title: Message Title Melissa Stone commented on PUP-9648 Re: Drop PSON support ping Nick Walker Charlie Sharpsteen is this something that users are relying on? It doesn't look like we have an actual deprecation warning for this yet. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.305621.1555690549000.51118.1588195320099%40Atlassian.JIRA.
Jira (PUP-9469) Remove the setting to turn off func 3x API validation
Title: Message Title Melissa Stone commented on PUP-9469 Re: Remove the setting to turn off func 3x API validation Justin Stoller Maggie Dreyer could you scope this removal? Are there any deprecations that need to be added to Puppet 6.16 before the setting is removed? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.294057.1548939109000.51115.1588195081275%40Atlassian.JIRA.
Jira (PUP-9426) Remove future_features logic
Title: Message Title Melissa Stone commented on PUP-9426 Re: Remove future_features logic Let's take this ticket and instead remove `future_features` wholesale. It's not guarding anything (after PUP-9405 is done). Rather than have future features be an all or nothing kind of thing, it's better that we ship features in y releases and allow users to have more fine-grained control over what is or is not enabled. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.291460.1547160478000.51085.1588194960087%40Atlassian.JIRA.
Jira (PUP-9407) Don't backup to the local filebucket by default
Title: Message Title Melissa Stone commented on PUP-9407 Re: Don't backup to the local filebucket by default This is a good thing to pull into Puppet 7. In addition to changing the default value, we should add a comment stating that it's the users responsibility to ensure the backup does not grow out of hand. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.291105.154707498.51054.1588194600029%40Atlassian.JIRA.
Jira (PUP-9405) Remove Future Feature flag for @prefetch_failed_providers in transaction.rb
Title: Message Title Melissa Stone commented on PUP-9405 Re: Remove Future Feature flag for @prefetch_failed_providers in transaction.rb Based on Charlie's comment in https://tickets.puppetlabs.com/browse/PUP-8962?focusedCommentId=600721=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-600721, we want the output if `:future_features` is true. To make this happen, we should remove the `unless ...` on line 387: https://github.com/puppetlabs/puppet/blob/12ac708d12e12aa0513348872ea0cec36701b5f8/lib/puppet/transaction.rb#L387 In addition, when we rescue `LoadError, Puppet::MissingCommand`, we also want to add the failed provider class to `@prefetch_failed_providers`, which is what is being referred to when we talk about collapsing the clauses. The other thing, instead of catching LoadError, we should be catching ScriptError, which is the parent of LoadError Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.290960.1546996315000.51044.1588194240143%40Atlassian.JIRA.
Jira (PUP-9309) Remove unused AST class SublocatedExpression
Title: Message Title Maggie Dreyer commented on PUP-9309 Re: Remove unused AST class SublocatedExpression Honestly not sure... Inclined to say no, though. I don't fully understand the statement about why it couldn't be removed previously though, so we should make sure we have a grasp on that before answering that. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.284713.1542018073000.51043.1588194240102%40Atlassian.JIRA.
Jira (PUP-9262) Remove fine grained file and environment timeouts
Title: Message Title Justin Stoller commented on PUP-9262 Re: Remove fine grained file and environment timeouts We've been talking more about environment ttls lately with the recent file-sync work. I think after this upcoming release we can look into whether the environment-ttl work will be doable in the pre-7 timeframe and if not we can remove the deprecation notice. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.282027.1540333474000.51006.1588193820024%40Atlassian.JIRA.
Jira (PUP-9309) Remove unused AST class SublocatedExpression
Title: Message Title Melissa Stone commented on PUP-9309 Re: Remove unused AST class SublocatedExpression Maggie Dreyer does a deprecation warning need to be filed before this class is removed? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.284713.1542018073000.51004.1588193580757%40Atlassian.JIRA.
Jira (PUP-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Melissa Stone commented on PUP-8014 Re: Create an environment_ttl setting to clear short-lived puppet environments from memory Nick Walker it sounds like you want per-environment control? Is what you're proposing in this ticket still a direction you want to go in? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.214193.1506980344000.50986.1588193460083%40Atlassian.JIRA.
Jira (PUP-9262) Remove fine grained file and environment timeouts
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9262 Remove fine grained file and environment timeouts Change By: Melissa Stone Team: Coremunity Froyo Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.282027.1540333474000.50983.1588193280980%40Atlassian.JIRA.
Jira (PUP-10292) external trusted data is executed for file_content requests
Title: Message Title Reid Vandewiele assigned an issue to Unassigned Puppet / PUP-10292 external trusted data is executed for file_content requests Change By: Reid Vandewiele Assignee: Reid Vandewiele Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.346028.1581515567000.50984.1588193281023%40Atlassian.JIRA.
Jira (PUP-9262) Remove fine grained file and environment timeouts
Title: Message Title Melissa Stone commented on PUP-9262 Re: Remove fine grained file and environment timeouts Justin Stoller we should figure out what we want to do with this soon. Either we should remove the deprecation warning, or we should remove the fine-grained control. Coremunity doesn't have enough context on the work to make this decision. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.282027.1540333474000.50959.1588193220094%40Atlassian.JIRA.
Jira (PUP-8014) Create an environment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8014 Create an environment_ttl setting to clear short-lived puppet environments from memory Change By: Josh Cooper Team: Coremunity Froyo Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.214193.1506980344000.50957.1588193160239%40Atlassian.JIRA.
Jira (PUP-7582) Make attempt to export or virtualize a class an error
Title: Message Title Melissa Stone updated an issue Puppet / PUP-7582 Make attempt to export or virtualize a class an error Change By: Melissa Stone Sub-team: Language Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.19.1495458026000.50948.1588193040053%40Atlassian.JIRA.
Jira (PUP-7582) Make attempt to export or virtualize a class an error
Title: Message Title Melissa Stone updated an issue Puppet / PUP-7582 Make attempt to export or virtualize a class an error Change By: Melissa Stone Team: Froyo Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.19.1495458026000.50949.1588193040096%40Atlassian.JIRA.
Jira (PUP-6645) Remove the hiera_xxx functions
Title: Message Title Melissa Stone assigned an issue to Josh Cooper Puppet / PUP-6645 Remove the hiera_xxx functions Change By: Melissa Stone Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.148538.1471963467000.50947.1588192980613%40Atlassian.JIRA.
Jira (PUP-7582) Make attempt to export or virtualize a class an error
Title: Message Title
Melissa Stone commented on PUP-7582
Re: Make attempt to export or virtualize a class an error
Hey Ben Ford! Question for you on this one. It looks like we do support virtualized classes in a sense in puppet. Josh Cooper and I are trying to figure out the best path forward on this. Currently, following the example in the description of PUP-1606, I can get the virtual class to notify successfully. It only errors out when I include `--strict=error`. ``` ➜ puppet git:(master) ✗ cat iclass.pp class vclass { notify {"vclass": message => "I've been realized" } } class iclass { @class {"vclass": } } class {"iclass":} ➜ puppet git:(master) ✗ be ./bin/puppet apply --debug iclass.pp Debug: Runtime environment: puppet_version=6.16.0, ruby_version=2.3.8, run_mode=user, default_encoding=UTF-8 Debug: Loading external facts from /Users/melissa/.puppetlabs/opt/puppet/cache/facts.d Debug: Facter: Found no suitable resolves of 1 for ec2_metadata . . . Debug: Facter: value for filesystems is still nil Debug: Facter: value for ipaddress6 is still nil Debug: Reset text domain to :production Warning: Classes are not virtualizable (file: /Users/melissa/workdir/puppet/iclass.pp, line: 8, column: 3) Notice: Compiled catalog for pyewacket.vpn.puppet.net in environment production in 0.04 seconds Debug: Creating default schedules Debug: Loaded state in 0.00 seconds Debug: Loaded state in 0.00 seconds Info: Applying configuration version '1588192102' Notice: I've been realized Notice: /Notify[vclass]/message: defined 'message' as 'I\'ve been realized' Debug: Finishing transaction 70323370342720 Debug: Storing state Debug: Pruned old state cache entries in 0.00 seconds Debug: Stored state in 0.00 seconds Notice: Applied catalog in 0.01 seconds Debug: Applying settings catalog for sections reporting, metrics Debug: Finishing transaction 70323644029760 Debug: Received report to process from pyewacket.vpn.puppet.net Debug: Processing report from pyewacket.vpn.puppet.net with processor Puppet::Reports::Store ➜ puppet git:(master) ✗ be ./bin/puppet apply --debug iclass.pp --strict error Debug: Runtime environment: puppet_version=6.16.0, ruby_version=2.3.8, run_mode=user, default_encoding=UTF-8 Debug: Loading external facts from /Users/melissa/.puppetlabs/opt/puppet/cache/facts.d . . . Debug: Facter: value for ipaddress6 is still nil Debug: Reset text domain to :production Error: Could not parse for environment production: Classes are not virtualizable (file: /Users/melissa/workdir/puppet/iclass.pp, line: 8, column: 3) on node pyewacket.vpn.puppet.net ``` Circling back to Eric's question, what's the benefit of removing this? How many people might this break? The warning was introduced in 4.10.2, so that's good if we do decide to make puppet fail if the user is trying to use a virtualized class.
Add Comment
Jira (PUP-10470) Pass credentials in basic_auth hash
Title: Message Title Josh Cooper commented on PUP-10470 Re: Pass credentials in basic_auth hash https://github.com/puppetlabs/puppet/commit/12ac708d12e12aa0513348872ea0cec36701b5f8 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356870.1588005936000.50881.1588191300059%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Josh Cooper commented on PUP-10247 Re: Support ruby 2.7 Arpit sharma, Ed Marshall, Anthony Sottile note you can always (and should) install puppet-agent packages from our repositories as it contains a vendored ruby, openssl, etc that works on Focal. If you install from Ubuntu repos then you're going to get an older version of puppet with compatibility issues such as this. That said, we will be moving our vendored ruby to 2.7 at some point in the future, and the issues in this epic will need to be addressed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342962.1579675679000.50579.1588181700108%40Atlassian.JIRA.
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title Josh Cooper commented on PUP-7197 Re: make type aliases from modules available on the agent Ah, it's because puppet apply loads the types using a different loader, which has visibility to all of the modules in the load path for the environment and doesn't require them to be namespaced in the same way. But types on the agent-side have the same issue as 4x functions called via deferred like https://github.com/voxpupuli/puppet-vault_lookup/blob/master/lib/puppet/functions/vault_lookup/lookup.rb — the function needs to be in a directory named after the function. It may be possible to preserve the module namespace for the types mount and create a new agent-side loader that doesn't have the same limitation as the cache loader. I'll take a look. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.174775.1486632721000.50525.1588181160028%40Atlassian.JIRA.
Jira (PUP-10470) Pass credentials in basic_auth hash
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10470 Pass credentials in basic_auth hash Change By: Melissa Stone Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356870.1588005936000.50471.1588179960028%40Atlassian.JIRA.
Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4682 PuppetDB sync status doesn't get updated when finished Change By: Austin Blatt Release Notes Summary: Fixed a bug that would cause PE's sync to fail and never retry when one PuppetDB had been upgraded and the other had not. Now it will fail and retry. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354044.1585853662000.50454.1588179720029%40Atlassian.JIRA.
Jira (PUP-10451) Prepare release announcement (Puppet Platform 6.15.0)
Title: Message Title Claire Cadman commented on PUP-10451 Re: Prepare release announcement (Puppet Platform 6.15.0) Looks good to me Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356747.1587775913000.50380.1588178760022%40Atlassian.JIRA.
Jira (PUP-10461) Prepare release announcement (Puppet Platform 5.5.20)
Title: Message Title Claire Cadman commented on PUP-10461 Re: Prepare release announcement (Puppet Platform 5.5.20) Looks good to me Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356780.1587776061000.50379.1588178700061%40Atlassian.JIRA.
Jira (PDB-4681) Investigate which pg user owns on demand partitions
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4681 Investigate which pg user owns on demand partitions Change By: Austin Blatt Fix Version/s: PDB 6.10.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353717.1585759029000.50366.1588178220143%40Atlassian.JIRA.
Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4682 PuppetDB sync status doesn't get updated when finished Change By: Austin Blatt Fix Version/s: PDB 6.10.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354044.1585853662000.50363.1588178100147%40Atlassian.JIRA.
Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4682 PuppetDB sync status doesn't get updated when finished Change By: Austin Blatt Fix Version/s: PDB 5.2.14 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354044.1585853662000.50362.1588178100105%40Atlassian.JIRA.
Jira (PDB-4708) Draft PuppetDB release notes
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4708 Draft PuppetDB release notes Change By: Austin Blatt Sprint: HA Team 2020-05-05 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357181.1588176131000.50284.1588176360054%40Atlassian.JIRA.
Jira (PDB-4708) Draft PuppetDB release notes
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4708 Draft PuppetDB release notes Issue Type: Task Assignee: Unassigned Created: 2020/04/29 9:02 AM Fix Versions: PDB n/a Priority: Normal Reporter: Austin Blatt We need to draft release notes for 5.2.14 and 6.10.0. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4708) Draft PuppetDB release notes
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4708 Draft PuppetDB release notes Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357181.1588176131000.50282.1588176180291%40Atlassian.JIRA.
Jira (PDB-4694) Update winston (PuppetDB 6.10.0)
Title: Message Title Austin Blatt commented on PDB-4694 Re: Update winston (PuppetDB 6.10.0) It looks like going forward we will be writing our own release notes, we should add a new Winston ticket to have these drafted. Be sure to add a line about how to run the contibutors in git log script. Currently, I believe these need to be drafted the day before "Ready to Ship" so the docs team can review them. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356775.1587776001000.50267.1588175460026%40Atlassian.JIRA.
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Claire Cadman commented on PUP-9251 Re: Deprecate 'application orchestration' features Josh Cooper Actually the 2018.1 docs will stay on the site and have a stable link. We've started archiving old docs, but they keep the same URL: https://puppet.com/docs/pe/latest/archived_pe_docs.html Will that work? Even though it will still have a version, the URL won't change. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.281366.1539943536000.50262.1588175220151%40Atlassian.JIRA.
Jira (PDB-4694) Update winston (PuppetDB 6.10.0)
Title: Message Title Austin Blatt assigned an issue to Zachary Kent PuppetDB / PDB-4694 Update winston (PuppetDB 6.10.0) Change By: Austin Blatt Assignee: Austin Blatt Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356775.1587776001000.50261.1588175220107%40Atlassian.JIRA.
Jira (PDB-4694) Update winston (PuppetDB 6.10.0)
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4694 Update winston (PuppetDB 6.10.0) Change By: Austin Blatt Assignee: Zachary Kent Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356775.1587776001000.50259.1588175160026%40Atlassian.JIRA.
Jira (PUP-10419) Support disable module with dnfmodule package provider
Title: Message Title
Dorin Pleava commented on PUP-10419
Re: Support disable module with dnfmodule package provider
After some discussion with the team, we think the best method to disable a dnf module, is to create a new value for ensure field, only available for dnf module.
"package { 'package_name':
ensure => 'disabled',
provider => 'dnfmodule'
}"
Some other alternatives would have been:
Create a new parameter 'disable_stream=true', but that would lead to additional checks/complexity regarding the ensure parameter.
Creating a new resource, but most likely we would end up in the same situation where we would like to enable a stream, but not install the profile, so we would need the enable_only field again.
Add Comment
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title
David Schmitt commented on PUP-7197
Re: make type aliases from modules available on the agent
Josh Cooper your comment about the stdlib types not being in the "correct" directory seems to raise another issue: as the stdlib types are laid out currently works with puppet apply:
david@zion:~/git/puppetlabs-stdlib (master)$ ls spec/fixtures/modules/stdlib/types/
absolutepath.pp compat filesource.pp httpsurl.pp mac.pp port unixpath.pp
base32.ppensure fqdn.pphttpurl.pp objectstore port.ppwindowspath.pp
base64.ppfilemode.pp host.ppip objectstore.pp syslogfacility.pp yes_no.pp
david@zion:~/git/puppetlabs-stdlib (master)$ pdk bundle exec puppet apply --modulepath spec/fixtures/modules --verbose -e 'notice("https://foo" =~ Stdlib::HTTPSUrl)'
pdk (INFO): Using Ruby 2.5.7
pdk (INFO): Using Puppet 6.13.0
Info: Loading facts
Info: Loading facts
Notice: Scope(Class[main]): true
Notice: Compiled catalog for zion in environment production in 0.05 seconds
Jira (FACT-2247) networking fact for Fedora
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2247 networking fact for Fedora Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.338974.1576066004000.50151.1588169580033%40Atlassian.JIRA.
Jira (FACT-2479) Uptime facts on LXC get the uptime from the host OS and not the container.
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2479 Uptime facts on LXC get the uptime from the host OS and not the container. Change By: Oana Tanasoiu Epic Link: FACT-2508 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.350675.1584693591000.50150.1588169460025%40Atlassian.JIRA.
Jira (PUP-10461) Prepare release announcement (Puppet Platform 5.5.20)
Title: Message Title Margaret Lee commented on PUP-10461 Re: Prepare release announcement (Puppet Platform 5.5.20) The next point release in the Puppet 5.5 series, Puppet 5.5.20, is now available! The release contains security and bug fixes and minor improvements, including: Facter 3.11.13 released which allows you to cache custom facts Improved performance on the 'selmodule' provider Upgrades Ruby to 2.4.10 and much more! For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/5.5/release_notes.html Nick Walker same here, feel free to update to different highlights if you think there are better ones. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356780.1587776061000.50134.1588168320087%40Atlassian.JIRA.
Jira (PUP-10451) Prepare release announcement (Puppet Platform 6.15.0)
Title: Message Title Margaret Lee commented on PUP-10451 Re: Prepare release announcement (Puppet Platform 6.15.0) he next release in the Puppet 6 series, Puppet 6.15.0, is now available! The release contains security and bug fixes and minor improvements, including: Support for Ubuntu 20.04 support `SemVerRange` support for `yum`, `apt`, `pip` and `gem` package providers Partitioned reports table for better performance Facter 3.14.10 released and much more! For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html Nick Walker I picked a few to highlight from the release notes, feel free to change them if you think different ones would be better. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356747.1587775913000.50131.1588167840039%40Atlassian.JIRA.
Jira (FACT-2596) Update tests to use host method for test -f command
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2596 Update tests to use host method for test -f command Issue Type: Improvement Assignee: Unassigned Created: 2020/04/29 6:26 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2595) Update tests to use host method for env command
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2595 Update tests to use host method for env command Issue Type: Improvement Assignee: Unassigned Created: 2020/04/29 6:26 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2594) Update tests to use host method for grep command
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2594 Update tests to use host method for grep command Issue Type: Improvement Assignee: Unassigned Created: 2020/04/29 6:25 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2593) Update tests to use host method for hostname command
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2593 Update tests to use host method for hostname command Issue Type: Improvement Assignee: Unassigned Created: 2020/04/29 6:25 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2592) Update tests to use host method for cat command
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2592 Update tests to use host method for cat command Issue Type: Improvement Assignee: Unassigned Created: 2020/04/29 6:22 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2591) Update tests to use host method for which command
Title: Message Title Sebastian Miclea moved an issue Facter / FACT-2591 Update tests to use host method for which command Change By: Sebastian Miclea Key: BKR FACT - 1648 2591 Project: Beaker Facter Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357165.1588166431000.50105.1588166520043%40Atlassian.JIRA.
Jira (FACT-2536) facter 4.x fails on Archlinux
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2536 facter 4.x fails on Archlinux Change By: Oana Tanasoiu Epic Link: FACT-2508 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354178.1585993672000.50097.1588165920032%40Atlassian.JIRA.
Jira (FACT-2536) facter 4.x fails on Archlinux
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2536 facter 4.x fails on Archlinux Change By: Oana Tanasoiu Priority: Normal High Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354178.1585993672000.50096.1588165860030%40Atlassian.JIRA.
Jira (FACT-2590) No facts are displayed on Redhat 5 and Centos6
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2590 No facts are displayed on Redhat 5 and Centos6 Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357162.1588165041000.50088.1588165080119%40Atlassian.JIRA.
Jira (FACT-2590) No facts are displayed on Redhat 5 and Centos6
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2590 No facts are displayed on Redhat 5 and Centos6 Issue Type: Bug Assignee: Unassigned Created: 2020/04/29 5:57 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (PUP-7163) regression - systemd provider does not honor documented enabled states
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-7163 regression - systemd provider does not honor documented enabled states Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Enabling 'indirect' services was causing idempotency issue in puppet due to systemd limitations. It was fixed by not allowing users to enable/disable such services and print a debug log instead. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.173739.1486008007000.50077.1588163280032%40Atlassian.JIRA.
Jira (PUP-10477) Remove non-local return from agent.rb
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-10477 Remove non-local return from agent.rb Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357118.158814853.50011.1588157580094%40Atlassian.JIRA.
Jira (PUP-10451) Prepare release announcement (Puppet Platform 6.15.0)
Title: Message Title Claire Cadman commented on PUP-10451 Re: Prepare release announcement (Puppet Platform 6.15.0) Nirupama Mantha Puppet 6.10.0 and Facter 3.14.10 release notes: https://docs.google.com/document/d/1jttwqo-uQwIt3yFQYsa7hs_SwFp-SZls_tSATgD9AvM/edit?usp=sharing These should also be up on our preview site later today. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356747.1587775913000.50008.1588157460077%40Atlassian.JIRA.
Jira (PUP-10461) Prepare release announcement (Puppet Platform 5.5.20)
Title: Message Title Claire Cadman commented on PUP-10461 Re: Prepare release announcement (Puppet Platform 5.5.20) Nirupama Mantha PR for Puppet 5.5.20 and Facter 3.11.13 release notes: https://github.com/puppetlabs/puppet-docs/pull/973 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356780.1587776061000.50005.1588157340023%40Atlassian.JIRA.
Jira (PUP-10463) Publish documentation and updates and release notes (Puppet Platform 5.5.20)
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10463 Publish documentation and updates and release notes (Puppet Platform 5.5.20) Change By: Claire Cadman (Initial planned release date: 2020-04-30)Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Puppet 5.5.20 and Facter 3.11.13 release notes PR: [https://github.com/puppetlabs/puppet-docs/pull/973]h1. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356783.1587776073000.50002.1588157100065%40Atlassian.JIRA.
Jira (PUP-10453) Publish documentation and updates and release notes (Puppet Platform 6.15.0)
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10453 Publish documentation and updates and release notes (Puppet Platform 6.15.0) Change By: Claire Cadman (Initial planned release date: 2020-04-30)Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Release notes: https://docs.google.com/document/d/1jttwqo-uQwIt3yFQYsa7hs_SwFp-SZls_tSATgD9AvM/edit?usp=sharing Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356750.1587775922000.49989.1588155480056%40Atlassian.JIRA.
Jira (PUP-10453) Publish documentation and updates and release notes (Puppet Platform 6.15.0)
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10453 Publish documentation and updates and release notes (Puppet Platform 6.15.0) Change By: Claire Cadman (Initial planned release date: 2020-04-30)Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out.Release notes draft : [ https://docs.google.com/document/d/1jttwqo-uQwIt3yFQYsa7hs_SwFp-SZls_tSATgD9AvM/edit?usp=sharing ] Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356750.1587775922000.49990.1588155480111%40Atlassian.JIRA.
Jira (PUP-10298) Add SemVerRange support to yum package provider
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-10298
Add SemVerRange support to yum package provider
Change By:
Gheorghe Popescu
Implement SemVerRange Version Range type support for the {{yum}} provider.Sample manifest with a range passed for a package:{code:title=|language=none|collapse=false} package { 'puppet-agent': # this will be parsed as: >= 6.0.0 < 6.1.0 ensure => SemVerRange('~> 6.0')} package { 'puppet-agent': ensure => SemVerRange( '>= 6.5' ) }package { 'puppet-agent': ensure => SemVerRange( '< 6.4' ) }package { 'puppet-agent': # this is a valid range which we can support ensure => SemVerRange( ' ~ > 6. 0 || ~> 6.11 4 <=7 ' ) }{code}The {{yum}} provider does not support a version range passed in the install command, so we have to:* find out the available versions for a specific package (usually with {{yum list --showduplicates}})* install the most recent package which respects the range.We should also make sure we don't take additional actions if the range is already satisfied (i.e. puppet apply with a {{SemVerRange}} should be idempotent)Sample code on how the ensure property can be treated inside the provider:{code:title=|language=none|collapse=false}if @resource.should(:ensure).is_a?(SemanticPuppet::VersionRange) # these should be sorted in descending order _, *versions = `yum list -d 0 -e 1 --showduplicates #{@resource.name} | awk '{print $2}'`.split range = @resource.should(:ensure) available.versions.any? { |version| range.include?(version.to_stable) }end{code}Example {{yum install}} with a specific version (package name and version are joined by a dash):{noformat}yum install puppet-agent-6.0.4-1.el7{noformat} Limitations of Version Ranges: YUM provider is using RPM to compare package versions and no epoch is considered `zero` epoch. As a consequence to this we need to specify also the epoch if we don't want the default behaviourFor example:- *>1 <2* will search in (0:1, 0:2) interval- *>1 <1:2* will search in (0:1, 1:2) interval, eligible versions will be searched in bot 0 and 1 epoch- *>1* will consider any version form epoch 0, greater that 1 and any version with epoch > 0
Add Comment
Jira (PUP-10298) Add SemVerRange support to yum package provider
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-10298
Add SemVerRange support to yum package provider
Change By:
Gheorghe Popescu
Implement Version Range type support for the {{yum}} provider.Sample manifest with a range passed for a package: {code:title=|language=none|collapse=false} package { 'puppet-agent': ensure => '>= 6.5'}package { 'puppet-agent': ensure => '< 6.4'}package { 'puppet-agent': ensure => '>6.4 <=7'}{code} The {{yum}} provider does not support a version range passed in the install command, so we have to: * find out the available versions for a specific package (usually with {{yum list --showduplicates}})* install the most recent package which respects the range.We should also make sure we don't take additional actions if the range is already satisfied (i.e. puppet apply with a {{SemVerRange}} should be idempotent)Sample code on how the ensure property can be treated inside the provider: {code:title=|language=none|collapse=false}if @resource.should(:ensure).is_a?(SemanticPuppet::VersionRange) # these should be sorted in descending order _, *versions = `yum list -d 0 -e 1 --showduplicates #{@resource.name} | awk '{print $2}'`.split range = @resource.should(:ensure) available.versions.any? { |version| range.include?(version.to_stable) }end{code} Example {{yum install}} with a specific version (package name and version are joined by a dash): {noformat} yum install puppet-agent-6.0.4-1.el7{noformat} Limitations of Version Ranges: YUM provider is using RPM to compare package versions and no epoch is considered `zero` epoch. As a consequence to this we need to specify also the epoch if we don't want the default behaviourFor example:- *>1 <2* will search in (0:1, 0:2) interval- *>1 <1:2* will search in (0:1, 1:2) interval, eligible versions will be searched in bot 0 and 1 epoch- *>1* will consider any version form epoch 0, greater that 1 and any version with epoch > 0
Add Comment
Jira (FACT-2587) Puppet facts missing on facter 3.10.0 with OSP 6.13.0
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2587 Puppet facts missing on facter 3.10.0 with OSP 6.13.0 Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357029.158809312.49916.1588150140032%40Atlassian.JIRA.
Jira (FACT-2587) Puppet facts missing on facter 3.10.0 with OSP 6.13.0
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2587 Puppet facts missing on facter 3.10.0 with OSP 6.13.0 Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357029.158809312.49915.1588150020026%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10351 Puppet Agent fails to self-restart on config change or update Change By: Mihai Buzgau Sprint: NW - 2020-04-01, NW - 2020-04-15, NW - 2020-04-29 , NW - 2020-05-13 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348520.1583329295000.49912.1588149660171%40Atlassian.JIRA.
Jira (PUP-7663) User resource expiry incorrect on SLES 11
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-7663 User resource expiry incorrect on SLES 11 Change By: Mihai Buzgau Sprint: NW - 2020-04-29 , NW - 2020-05-13 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.195934.149746173.49910.1588149660073%40Atlassian.JIRA.
Jira (PUP-10284) Update Public-facing Puppet docs to include Ubuntu 20.04 (x64)
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10284 Update Public-facing Puppet docs to include Ubuntu 20.04 (x64) Change By: Mihai Buzgau Sprint: NW - 2020-04-01, NW - 2020-04-15, NW - 2020-04-29 , NW - 2020-05-13 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.345559.1581083033000.49913.1588149660216%40Atlassian.JIRA.
Jira (PUP-7163) regression - systemd provider does not honor documented enabled states
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-7163 regression - systemd provider does not honor documented enabled states Change By: Mihai Buzgau Sprint: Client 2016-06-29, NW - 2020-04-29 , NW - 2020-05-13 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.173739.1486008007000.49914.1588149660259%40Atlassian.JIRA.
Jira (PUP-10419) Support disable module with dnfmodule package provider
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10419 Support disable module with dnfmodule package provider Change By: Mihai Buzgau Sprint: NW - 2020-04-29 , NW - 2020-05-13 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355472.1586866878000.49911.1588149660127%40Atlassian.JIRA.
Jira (PUP-10477) Remove non-local return from agent.rb
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10477 Remove non-local return from agent.rb Change By: Gheorghe Popescu Ideally we should never do a non-local return. Code to be assesed assessed :- https://github.com/puppetlabs/puppet/commit/ce74cd97085c3d3bd7b4888c80bcbf14ebfdfa2- https://github.com/puppetlabs/puppet/commit/10d89dc463ebe8d31cee3a3603e924ae614f754a- https://github.com/puppetlabs/puppet/commit/42f1f27d914576be95b8745b6015897993f9aea3.It would be great to clean that up so that nil is always returned due to an error, so that [Puppet::Application::Agent consistently exits with 1.|https://github.com/puppetlabs/puppet/blob/42f1f27d914576be95b8745b6015897993f9aea3/lib/puppet/application/agent.rb#L360-L374] Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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-10477) Remove non-local return from agent.rb
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10477 Remove non-local return from agent.rb Change By: Gheorghe Popescu Ideally we should never do a non-local return. It was added by mistake in Code to be assesed:- https://github.com/puppetlabs/puppet/commit/ce74cd97085c3d3bd7b4888c80bcbf14ebfdfa2 , was made worse in - https://github.com/puppetlabs/puppet/commit/10d89dc463ebe8d31cee3a3603e924ae614f754a and a "different but equally wrong" approach was taken in - https://github.com/puppetlabs/puppet/commit/42f1f27d914576be95b8745b6015897993f9aea3.It would be great to clean that up so that nil is always returned due to an error, so that [Puppet::Application::Agent consistently exits with 1.|https://github.com/puppetlabs/puppet/blob/42f1f27d914576be95b8745b6015897993f9aea3/lib/puppet/application/agent.rb#L360-L374] Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (PUP-10477) Remove non-local return from agent.rb
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10477 Remove non-local return from agent.rb Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357118.158814853.49905.1588148640050%40Atlassian.JIRA.
Jira (PUP-10477) Remove non-local return from agent.rb
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10477 Remove non-local return from agent.rb Change By: Gheorghe Popescu Ideally we should never do a non-local return. It was added by mistake in https://github.com/puppetlabs/puppet/commit/ce74cd97085c3d3bd7b4888c80bcbf14ebfdfa2, was made worse in https://github.com/puppetlabs/puppet/commit/10d89dc463ebe8d31cee3a3603e924ae614f754a and a "different but equally wrong" approach was taken in https://github.com/puppetlabs/puppet/commit/42f1f27d914576be95b8745b6015897993f9aea3.It would be great to clean that up so that nil is always returned due to an error, so that [ TODO Puppet::Application::Agent consistently exits with 1.|https://github.com/puppetlabs/puppet/blob/42f1f27d914576be95b8745b6015897993f9aea3/lib/puppet/application/agent.rb#L360-L374 ] Add description Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-10477) Remove non-local return from agent.rb
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-10477 Remove non-local return from agent.rb Issue Type: Task Assignee: Unassigned Created: 2020/04/29 1:22 AM Priority: Normal Reporter: Mihai Buzgau [TODO] Add description Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10433) Zypper provider doesn't recognize --no-gpg-checks as global option
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10433 Zypper provider doesn't recognize --no-gpg-checks as global option Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356395.1587577044000.49897.1588147080028%40Atlassian.JIRA.
