Jira (PUP-10948) puppet node find does not honour node_name
Title: Message Title Kaushal Kumar commented on PUP-10948 Re: puppet node find does not honour node_name Hi Josh Cooper , Thanks for your response. I was trying to get the environment associated to each node as there could be multiple environment available during installation. The docs @ https://puppet.com/docs/puppet/6.21/environments_about.html states To look up which environment a node is in, run puppet node find on the Puppet Server host node, replacing with the node's exact name. Alternatively, run puppet node find --render_as json | jq .environment to render the output as JSON and return only the environment name Even the help of this command this does not indicates what you have described above. So there are couple of questions 1. Can we get the documentation fixed in the environments_about.html and man page of this command. 2. What will be your suggestion to get the environment related to different nodes in puppet setup. What I could think was to connect to each node and query the node information via puppet node find, but that could involve connecting to several machines. Is there a better way to do this? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2958) Fact names with dots shouldn't be converted to structured facts
Title: Message Title Josh Cooper created an issue Facter / FACT-2958 Fact names with dots shouldn't be converted to structured facts Issue Type: Bug Affects Versions: FACT 4.0.51 Assignee: Unassigned Created: 2021/03/04 8:09 PM Priority: Normal Reporter: Josh Cooper In Facter 3, dots are legal characters in fact names, so "a.b" is a valid fact name. The fact can then be used in a puppet manifest using $facts['a.b']. In Facter 4, dots in custom and external facts cause the fact to be converted to a structured fact. This breaks any puppet code that tries to resolve the fact: For example, given custom and executable external facts: mkdir -p /etc/facter/facts.d/ cat < /etc/facter/facts.d/dot.sh #!/bin/sh echo exe.bar=baz END
Jira (PUP-10952) Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-10952 Changing a Puppet setting in a catalog invalidates the env cache in multithreaded mode Change By: Maggie Dreyer Key: SERVER PUP - 2980 10952 Project: Puppet Server 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.390083.1614901848000.158117.1614904920038%40Atlassian.JIRA.
Jira (PDB-5053) Move sync expired resource_event filter to report ingest
Title: Message Title Zachary Kent commented on PDB-5053 Re: Move sync expired resource_event filter to report ingest As part of this work we'll want to make sure that the resource->skipped-resource-events function can't create resource_events which are older than the resource-event-ttl. This might happen naturally with work described above but we'll want to make sure to double check. 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.389887.1614814159000.158028.1614898260027%40Atlassian.JIRA.
Jira (PDB-5055) Add a new query param that returns EXPLAIN ANALYZE output for a given query
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5055 Add a new query param that returns EXPLAIN ANALYZE output for a given query Change By: Zachary Kent Labels: tsr-pdb-backlog 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.390060.1614896952000.158011.1614897180026%40Atlassian.JIRA.
Jira (PDB-5055) Add a new query param that returns EXPLAIN ANALYZE output for a given query
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5055 Add a new query param that returns EXPLAIN ANALYZE output for a given query Change By: Zachary Kent Acceptance Criteria: * New query param which causes any query to return EXPLAIN ANALYZE output* Tests which check that this param works across a handful of the query endpoints* Documentation explaining the new query param 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.390060.1614896952000.158010.1614897120090%40Atlassian.JIRA.
Jira (PDB-5055) Add a new query param that returns EXPLAIN ANALYZE output for a given query
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-5055 Add a new query param that returns EXPLAIN ANALYZE output for a given query Issue Type: Bug Assignee: Unassigned Created: 2021/03/04 2:29 PM Priority: Normal Reporter: Zachary Kent We want to expose the EXPLAIN ANALYZE option added to the TK PuppetDBServer query method in PDB-5042 externally via a query param. To add the query param we could follow the example in the initial drop-joins pr. This pr added a optimize_drop_unused_joins=true query parameter to allow clients to opt-in to drop-joins. Following a similar pattern should allow us to pass down a flag which should eventually hit the same path used in PDB-5042 which will return the JSON of an EXPLAIN ANALYZE for a given query. Add Comment
Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-2956
Facter should ensure core facts are resolved before loading custom facts
Change By:
Josh Cooper
Facter 4 calls {{Kernel.load}} on all custom ruby facts before core facts have been resolved. If the custom ruby facts has code outside a {{setcode}} block, then it's possible for core facts like {{Facter.value(:operatingsystem)}} to return nil, like FACT-2880.It is true that custom facts shouldn't misbehave that way, but a single misbehaving custom fact can prevent PE from managing itself. We also don't have tooling/validation to warn or prevent users from doing this, so there are many examples of it in practice.We should be more defensive about this. One way would be to ensure core facts are resolved before custom facts are loaded. It would still be possible for a custom fact with a higher weight to override the core fact, but at least the core fact would never have a nil value.Facter 3 didn't have this issue because core facts were implemented in C++ and evaluated before loading custom ruby facts. Due to this issue, puppet may not be able to manage services, because puppet selects {{base}} as the default service provider instead of {{systemd}}:{noformat}change from 'stopped' to 'running' failed: Services must specify a start command or a binary (corrective){noformat}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts
Title: Message Title Josh Cooper updated an issue Facter / FACT-2956 Facter should ensure core facts are resolved before loading custom facts Change By: Josh Cooper Fix Version/s: FACT 4.0.52 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.389854.1614799263000.157871.1614891900187%40Atlassian.JIRA.
Jira (PUP-10951) The operator '* =>' in a Virtual Query is not supported.
Title: Message Title
Steven Pritchard created an issue
Puppet / PUP-10951
The operator '* =>' in a Virtual Query is not supported.
Issue Type:
Bug
Affects Versions:
PUP 7.4.1
Assignee:
Unassigned
Components:
Language
Created:
2021/03/04 1:03 PM
Priority:
Normal
Reporter:
Steven Pritchard
On Puppet 7.4.1, I get "The operator '* =>' in a Virtual Query is not supported." from the following code:
$services.each |$key, $value| {
if defined(Service[$key]) {
Service <| title == $key |> {
* => $value,
}
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Josh Cooper updated an issue Facter / FACT-2944 During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Change By: Josh Cooper Fix Version/s: FACT 4.0.52 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.387583.1613309929000.157800.1614888660108%40Atlassian.JIRA.
Jira (PUP-10948) puppet node find does not honour node_name
Title: Message Title Josh Cooper commented on PUP-10948 Re: puppet node find does not honour node_name puppet node find will only tell you about the current node you're running on. When you enter an invalid node, the command assumes you mean the current node is named that. So it combines the current nodes facts with that name. If you want to know if a node exists, then you're probably better off querying for the cert for that node: # curl -kf https://:8140/puppet-ca/v1/certificate/doesntexist curl: (22) The requested URL returned error: 404 Not Found # echo $? 22 Note puppetserver's default auth.conf doesn't allow HEAD requests, so you might want to change that. Or query for the node in puppetdb: https://puppet.com/docs/puppetdb/latest/api/query/v4/nodes.html#pdbqueryv4nodes Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (HI-621) Need some help of call same hiera variable from multiple hiera files
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-621 Need some help of call same hiera variable from multiple hiera files Change By: Henrik Lindberg Priority: Major Low 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.389949.1614876617000.157636.1614881880098%40Atlassian.JIRA.
Jira (HI-621) Need some help of call same hiera variable from multiple hiera files
Title: Message Title Henrik Lindberg commented on HI-621 Re: Need some help of call same hiera variable from multiple hiera files You opened a ticket against the now deprecated Hiera version 3. It is also more of a usage question that an issue. You will get much better (and quicker) help from the community if you hop on to puppet's slack and ask for help there. 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.389949.1614876617000.157635.1614881880047%40Atlassian.JIRA.
Jira (PUP-10950) unless should support sensitive data for any type
Title: Message Title
Sheena Tharakanparampil updated an issue
Puppet / PUP-10950
unless should support sensitive data for any type
Change By:
Sheena Tharakanparampil
*Puppet Version:6.22.0* (was able to reproduce the problem on puppetagent6 puppet6 -nightly and puppetagent7 puppet7 -nightly) *OS Name/Version:Ubuntu 18.04 (*on all OSes*)**Sensitive masking is not implemented in core puppet at the points where the module needs it:*Using 'Sensitive' in 'unless' throws the following error {code:java} Unable to mark 'unless' as sensitive: unless is a parameter and not a property, and cannot be automatically redacted.{code} *Steps to reproduce the problem*Install the latest version of postgresql module (v6.10.2 and above) which we uses sensitive for security fixes.puppet module install puppetlabs-postgresql --version 7.0.0Apply the following manifest {code:java} test.ppclass { 'postgresql::server': } postgresql::server::role { testuser: password_hash => postgresql::postgresql_password('testuser', 'testpw'), } puppet apply test.ppNotice: Compiled catalog for oval-secrecy.delivery.puppetlabs.net in environment production in 0.37 secondsWarning: /Postgresql_psql[ALTER ROLE testuser ENCRYPTED PASSWORD ]: Unable to mark 'unless' as sensitive: unless is a parameter and not a property, and cannot be automatically redacted.Notice: /Stage[main]/Main/Postgresql::Server::Role[testuser]/Postgresql_psql[CREATE ROLE testuser ENCRYPTED PASSWORD ]/command: changed [redacted] to [redacted]Notice: Applied catalog in 1.01 secondsroot@oval-secrecy:~#{code} *Desired Behavior:*unless should support sensitive data*Actual Behavior:*Throws the below error on unless *Unable to mark 'unless' as sensitive: unless is a parameter and not a property, and cannot be automatically redacted.*Found similar tickets for exec typehttps://tickets.puppetlabs.com/browse/PUP-8399Please let us know if you need more information.
Add Comment
Jira (PUP-10950) unless should support sensitive data for any type
Title: Message Title
Sheena Tharakanparampil created an issue
Puppet / PUP-10950
unless should support sensitive data for any type
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/03/04 10:15 AM
Priority:
Normal
Reporter:
Sheena Tharakanparampil
Puppet Version:6.22.0 (was able to reproduce the problem on puppetagent6-nightly and puppetagent7-nightly) OS Name/Version:Ubuntu 18.04 (*on all OSes)* Sensitive masking is not implemented in core puppet at the points where the module needs it: Using 'Sensitive' in 'unless' throws the following error Steps to reproduce the problem Install the latest version of postgresql module (v6.10.2 and above) which we uses sensitive for security fixes. puppet module install puppetlabs-postgresql --version 7.0.0 Apply the following manifest
test.pp
class { 'postgresql::server': }
postgresql::server::role { testuser:
password_hash => postgresql::postgresql_password('testuser', 'testpw'),
}
Jira (PUP-10889) Explicitly set default ciphersuites to avoid surprises
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10889 Explicitly set default ciphersuites to avoid surprises Change By: Josh Cooper Release Notes Summary: Adds a "ciphers" puppet setting to configure which TLS ciphersuites the agent supports. The default set of ciphersuites is the same as what it was before this change, but the list of ciphersuites can be made more restricted if desired, such as to only accept TLS v1.2 or greater ciphersuites. 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.386476.1612552318000.157630.1614881640189%40Atlassian.JIRA.
Jira (PUP-10945) Change the master -> server in Server used http code
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10945 Change the master -> server in Server used http code Change By: Justin Stoller Team: 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.389566.1614715872000.157604.1614880500197%40Atlassian.JIRA.
Jira (PUP-10945) Change the master -> server in Server used http code
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10945 Change the master -> server in Server used http code Change By: Justin Stoller Sprint: Froyo - 03/10/2021 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.389566.1614715872000.157605.1614880500244%40Atlassian.JIRA.
Jira (PUP-10945) Change the master -> server in Server used http code
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10945 Change the master -> server in Server used http code Change By: Justin Stoller Story Points: 1 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.389566.1614715872000.157599.1614880440037%40Atlassian.JIRA.
Jira (FACT-2953) os codename should use parent os codename
Title: Message Title Charlie Sharpsteen commented on FACT-2953 Re: os codename should use parent os codename Using VERSION_CODENAME to populate os.distro.codename if it is present in the os-release file seems reasonable to me as it is specified in the documentation for os-release: https://man7.org/linux/man-pages/man5/os-release.5.html 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.389690.1614739764000.157496.1614877380128%40Atlassian.JIRA.
Jira (HI-621) Need some help of call same hiera variable from multiple hiera files
Title: Message Title Karthik Keshav M updated an issue Hiera / HI-621 Need some help of call same hiera variable from multiple hiera files Change By: Karthik Keshav M I've a hiera variables called profiles::apache::ssl_karthik in many files but different contents likeprofiles::apache::ssl_karthik present in context/m1.eyaml, context/m2.eyaml, context/m3.eyaml file with different contents I want to take the all those hiera's values (but same hiera lookup variable name ) from different eyaml file and keep it in single file using file_resource. is it possible? Basically combine the different certs present in multiple yaml files (but it is having same hiera variable name with different contents) to a pem file. 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
Jira (HI-621) Need some help of call same hiera variable from multiple hiera files
Title: Message Title Karthik Keshav M created an issue Hiera / HI-621 Need some help of call same hiera variable from multiple hiera files Issue Type: Task Assignee: Unassigned Created: 2021/03/04 8:50 AM Priority: Major Reporter: Karthik Keshav M I've a hiera variables called profiles::apache::ssl_karthik in many files but different contents like profiles::apache::ssl_karthik present in context/m1.eyaml, context/m2.eyaml, context/m3.eyaml file with different contents I want to take the all those hiera's values (but same hiera variable) from different eyaml file and keep it in single file using file_resource. is it possible? Basically combine the different certs present in multiple yaml files (but it is having same hiera variable name with different contents) to a pem file. Add Comment
Jira (PUP-10949) Puppet cannot parse systemd instances when list-unit-files output has an additional column
Title: Message Title Gabriel Nagy created an issue Puppet / PUP-10949 Puppet cannot parse systemd instances when list-unit-files output has an additional column Issue Type: Bug Assignee: Unassigned Created: 2021/03/04 7:53 AM Priority: Normal Reporter: Gabriel Nagy Puppet Version: 6.21.1/7.4.1 Puppet Server Version: n/a OS Name/Version: Fedora 32/Ubuntu 20.04 Some time ago the output of systemctl list-unit-files changed to include an additional column. Previous output (on CentOS 8): UNIT FILE STATE arp-ethers.service disabled auditd.service enabled auth-rpcgss-module.service static Current output (on Fedora 32 and Ubuntu 20.04):
Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts
Title: Message Title Gheorghe Popescu commented on FACT-2956 Re: Facter should ensure core facts are resolved before loading custom facts Hello, We compared Facter 3 and Facter 4 and found an issue in the way `Facter.value` is implemented. On Facter 3, search is done in multiple steps, and the next step is executed only if the previous one was not able to resolve the fact: search in the internal collection load the `fact_name.rb` from the configured custom directories load all the core facts, external facts and env facts load all custom facts Calling `Facter.value(:os)` will: search for `os` in its internal collection load `custom_dir/os.rb` load core, external and env facts Calling `Facter.value(:custom_fact)` will: search for `custom_fact` in its internal collection load `custom_dir/custom_fact.rb` load core, external and env facts load all custom facts On Facter 4, when `Facter.value` is called, Facter will load all the core facts and all the custom facts, then will resolve only the facts that match the requested query. We are working on porting the same searching mechanism form Facter 3 to Facter 4 which is preventing the load of all custom facts when a core fact is requested. Add Comment
Jira (FACT-2957) Add facter 3 support for Rocky Linux
Title: Message Title Gabriel Nagy created an issue Facter / FACT-2957 Add facter 3 support for Rocky Linux Issue Type: New Feature Assignee: Unassigned Created: 2021/03/04 6:28 AM Priority: Normal Reporter: Gabriel Nagy 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.389927.161486
Jira (PUP-10948) puppet node find does not honour node_name
Title: Message Title Kaushal Kumar created an issue Puppet / PUP-10948 puppet node find does not honour node_name Issue Type: Bug Affects Versions: PUP 6.20.0 Assignee: Unassigned Created: 2021/03/04 5:17 AM Priority: Normal Reporter: Kaushal Kumar Puppet Version: 6.20 Puppet Server Version: 6.15.1 OS Name/Version: CentOS Linux version 8 I am using puppet v6.20.0 and am executing sudo puppet node find to get the information of a node from puppet master. This command returns a node information even if an invalid node name (or node name which does not exists) is provided to this command. Is there any other argument which has to be provided to this. Desired Behavior: node find must not provide information about unknown nodes Actual Behavior: node find returns the node information irrespective of host name. Add Comment
Jira (PDB-4830) Big performance impact when upgrading to PuppetDB5/6
Title: Message Title Kamil Swoboda commented on PDB-4830 Re: Big performance impact when upgrading to PuppetDB5/6 Too bad Thanks for the replay though! If anything changes would be great if you'd post here 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.367361.1595856224000.157256.1614854880035%40Atlassian.JIRA.
Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-2956 Facter should ensure core facts are resolved before loading custom facts 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.389854.1614799263000.157186.1614849540037%40Atlassian.JIRA.
Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2956 Facter should ensure core facts are resolved before loading custom facts Change By: Mihai Buzgau Story Points: 5 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.389854.1614799263000.157183.1614849120048%40Atlassian.JIRA.
Jira (FACT-2956) Facter should ensure core facts are resolved before loading custom facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2956 Facter should ensure core facts are resolved before loading custom facts Change By: Mihai Buzgau Sprint: NW - 2021-03-17 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.389854.1614799263000.157184.1614849120093%40Atlassian.JIRA.
