Jira (PUP-5991) Unit tests fail on Windows if source exists in a root directory of dev
Title: Message Title Ethan Brown commented on PUP-5991 Re: Unit tests fail on Windows if source exists in a root directory of dev Modified PR merged to master in https://github.com/puppetlabs/puppet/commit/49356611b136c31e5c33456fdd743c7d7e1ca351 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5991) Unit tests fail on Windows if source exists in a root directory of dev
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-5991 Unit tests fail on Windows if source exists in a root directory of dev Change By: Ethan Brown Assignee: Rob Reynolds Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1341) Facter Throws Unhandled Exception when Run Under Unicode User
Title: Message Title Larissa Lane updated an issue Facter / FACT-1341 Facter Throws Unhandled Exception when Run Under Unicode User Change By: Larissa Lane Labels: i18n windows Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) literal interpolation function can appear only once in any data value
Title: Message Title Henrik Lindberg commented on HI-501 Re: literal interpolation function can appear only once in any data value I also added this to our "Language Triage" which means that it is on our radar screen, gets talked about and prioritized. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) literal interpolation function can appear only once in any data value
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-501 literal interpolation function can appear only once in any data value Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) literal interpolation function can appear only once in any data value
Title: Message Title
Henrik Lindberg commented on HI-501
Re: literal interpolation function can appear only once in any data value
HI-127
is also related. It shows the other workaround .- that is fixed in Hiera 3.1.0.
Workaround before literal(%) was added:
"%%{}"
This workaround was undocumented, untested and it broke in some releases. It is now supported as it ended up being what everyone had to use.
When it was broken, users found that %%{::} worked (out of chance). Then it broke because it was never intended to work.
HI-494
makes both of those variants work.
Towards the end of
HI-127
(long after ticket was closed, there is a report of a problem that looks like the one you are reporting.
Some people have gone so far as to use a rewrite backend (see original Redmine ticket linked from
HI-127
).
If you have the time, it would be great if you could test if hiera head of master branch works for you, or if you see the same problem.
We are very close to releasing Hiera 3.1.0 and if it does not work for you, then maybe the %%{} or %%{::} workaround will work until a better solution is found.
If you are on 4.x with support for lookup, you could try if it works there. The lookup functionality is a rewrite of hiera (among other things) and it resides in puppet. Longer term it will replace the hiera project (data is compatible with hiera 3.x).
I am reopening this as it is uncertain what the state of this particular problem is.
Add Comment
Jira (HI-501) literal interpolation function can appear only once in any data value
Title: Message Title Henrik Lindberg commented on HI-501 Re: literal interpolation function can appear only once in any data value I should have linked HI-497 which is also a duplicate of HI-494 . HI-494 broke the work around that is reported in HI-497 . The real issue here is that hiera interpolation has been quite broken in this respect for a long time, people instead use a work around, With all the work arounds being used in practice it is close to impossible to clean up bugs without causing silent breaking behavior. Will lookup some instruction how to work around the problem. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) literal interpolation function can appear only once in any data value
Title: Message Title
Johnson Earls commented on HI-501
Re: literal interpolation function can appear only once in any data value
I just looked at
HI-494
and this does not appear to be the same issue. That one is talking about a specific % interpolation whose function changed. I'm talking about a problem with % {literal()}
causing puppet catalog failures.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5996) acceptance: language/exported_resources.rb test fails when agent on master is run
Title: Message Title Jeremy Barlow commented on PUP-5996 Re: acceptance: language/exported_resources.rb test fails when agent on master is run William Hopper submitted a PR for this here - https://github.com/puppetlabs/puppet/pull/4743 - that was merged. We bumped to a newer version of our Puppet submodule from Puppet Server with this PR - https://github.com/puppetlabs/puppet-server/pull/938 - so hopefully we'll see things go green soon. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) literal interpolation function can appear only once in any data value
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-501
literal interpolation function can appear only once in any data value
Change By:
Henrik Lindberg
Summary:
{{%{ literal (...)}}} interpolation function can appear only once in any data value
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)}}} can appear only once in any data value
Title: Message Title
Henrik Lindberg assigned an issue to Unassigned
Hiera / HI-501
{{%{literal(...)}}} can appear only once in any data value
Change By:
Henrik Lindberg
Assignee:
Henrik Lindberg
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)}}} can appear only once in any data value
Title: Message Title
Henrik Lindberg commented on HI-501
Re: {{%{literal(...)}}} can appear only once in any data value
Thanks Johnson Earls for a very detailed error report.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)}}} can appear only once in any data value
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-501
{{%{literal(...)}}} can appear only once in any data value
Change By:
Henrik Lindberg
Summary:
{{%{literal(...) \ }}} can appear only once in any data value
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2492) update data service per ops deployment requirements
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2492 update data service per ops deployment requirements Change By: Wyatt Alt This ticket will be done when the following are implemented:logging: * in json form * when uploads happen * generate a uuid to stick in response headers * error handling when database is down, invalid requests, application misconfiguration deployment: * we can produce a jar and config file that can be run with java -jar foo.jar --config foo.conf * rename pdb-data-service Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2492) update data service per ops deployment requirements
Title: Message Title Wyatt Alt commented on PDB-2492 Re: update data service per ops deployment requirements cc Daniel Dreier Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2492) update data service per ops deployment requirements
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2492 update data service per ops deployment requirements Issue Type: Improvement Assignee: Unassigned Created: 2016/03/02 5:11 PM Priority: Normal Reporter: Wyatt Alt This ticket will be done when the following are implemented: logging: in json form when uploads happen generate a uuid to stick in response headers error handling when database is down, invalid requests, application misconfiguration deployment: we can produce a jar and config file that can be run with java -jar foo.jar --config foo.conf
Jira (PUP-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Henrik Lindberg Release Notes Summary: A regression was found where UTF-8 multibyte characters in a manifest would cause internal offsets to become out of sync. This problems in turn led to error messages pointing to the wrong location, and information services to use the wrong sections extracting selected parts of the source code ( . Node Classifier would present truncated/misaligned source snippets for default value expressions in Puppet Strings the UI , and Puppet String would present garbage in UI that shows classes and default value expressions) generated documentation, or in worst case crash . Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)\}}} can appear only once in any data value
Title: Message Title
Kylo Ginsberg updated an issue
Hiera / HI-501
{{%{literal(...)\}}} can appear only once in any data value
Change By:
Kylo Ginsberg
Scrum Team:
Language
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)\}}} can appear only once in any data value
Title: Message Title
Kylo Ginsberg commented on HI-501
Re: {{%{literal(...)\}}} can appear only once in any data value
Ping Henrik Lindberg.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)\}}} can appear only once in any data value
Title: Message Title
Kylo Ginsberg assigned an issue to Henrik Lindberg
Hiera / HI-501
{{%{literal(...)\}}} can appear only once in any data value
Change By:
Kylo Ginsberg
Assignee:
Jenny Mahmoudi Henrik Lindberg
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2123) PDB CLI Tooling Phase 1
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2123 PDB CLI Tooling Phase 1 Change By: Susan McNerney Scrum Team/s: PuppetDB This epic describes The user will be able to query PuppetDB, import/export their PuppetDB instance and check on the first implementation status of their PuppetDB CLI in PE instance . Current interaction with PuppetDb involves tedious curl commands, external utilities (like using puppetdbquery on the command line) and full PuppetDB installs (for import/export). This will provide a consistent interface for all of these interactions through one tool. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5902) Type mismatch describer should expand aliases
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5902 Type mismatch describer should expand aliases Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5901) Type mismatch describer should merge Enum expectations
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5901 Type mismatch describer should merge Enum expectations Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5986) Bad error for unresolved type in 4.x function API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5986 Bad error for unresolved type in 4.x function API Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5983) Environment Data Provider has different interpolation behavior than Hiera
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5983 Environment Data Provider has different interpolation behavior than Hiera Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5964) Improve how type mismatches are asserted and reported
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5964 Improve how type mismatches are asserted and reported Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)\}}} can appear only once in any data value
Title: Message Title
Johnson Earls commented on HI-501
Re: {{%{literal(...)\}}} can appear only once in any data value
I just tested, and this also affects Hiera version 3.0.6 as well.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)\}}} can appear only once in any data value
Title: Message Title
Johnson Earls updated an issue
Hiera / HI-501
{{%{literal(...)\}}} can appear only once in any data value
Change By:
Johnson Earls
Affects Version/s:
HI 3.0.6
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-24) Environment manifest setting, when a directory, is not recursing on subdirectories
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-24
Environment manifest setting, when a directory, is not recursing on subdirectories
Change By:
Peter Huene
Scope Change Category:
Found
Scope Change Reason:
Found after the parse command work on the native compiler was merged
Sprint:
Language Triage 2016-03-09 (Burn CF)
If an environment's {{manifest}} setting points at a directory (which is the default) , the native compiler is not recursing to find main manifests.The recursion needs to be done in the currently performed sort-order to make the traversal order predictable.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscri
Jira (NPUP-24) Environment manifest setting, when a directory, is not recursing on subdirectories
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-24 Environment manifest setting, when a directory, is not recursing on subdirectories Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1355) Fix build isolation for generated files
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1355 Fix build isolation for generated files Change By: Kylo Ginsberg Sprint: Client Triage 2016-04-10 (C++) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1357) puppet-agent build fails on facter unit test if bundle is installed
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1357 puppet-agent build fails on facter unit test if bundle is installed Change By: Kylo Ginsberg Sprint: Client Triage 2016-04-10 (C++) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5967) File type links documentation incorrectly references :ignore value
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5967 File type links documentation incorrectly references :ignore value Change By: Kylo Ginsberg Sprint: Client Triage 2016-03-23 (Bug Fixes) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5978) Deprecate static compiler
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5978 Deprecate static compiler Change By: Kylo Ginsberg Release Notes Summary: As part of the 4.4 documentation around static_catalogs we should mention that static_compiler is now deprecated. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5978) Deprecate static compiler
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5978 Deprecate static compiler Change By: Kylo Ginsberg Story Points: 1 0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5978) Deprecate static compiler
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5978 Deprecate static compiler Change By: Kylo Ginsberg Fix Version/s: PUP 4.x Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5978) Deprecate static compiler
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5978 Deprecate static compiler Change By: Kylo Ginsberg Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5968) Deprecate Symbol#<=> monkey patch
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5968 Deprecate Symbol#<=> monkey patch Change By: Kylo Ginsberg Sprint: Client Triage 2016-03-23 (Bug Fixes) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2123) PDB CLI Tooling Phase 1
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2123 PDB CLI Tooling Phase 1 Change By: Susan McNerney This epic describes the first implementation of PuppetDB CLI in PE. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Eric Sorenson updated an issue Facter / FACT-1356 External facts should be able to return structured data Change By: Eric Sorenson Fix Version/s: FACT 3.x Fix Version/s: FACT 3.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5926) launchd service provider doesn't implement status override.
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-5926 launchd service provider doesn't implement status override. Change By: Eric Sorenson Summary: Service resource ignoring launchd service provider doesn't implement status override. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5921) Deprecate source_permissions
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5921 Deprecate source_permissions Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5920) Implement pluginsync of external facts without using source_permissions
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5920 Implement pluginsync of external facts without using source_permissions Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5992) Systemd service provider do not support custom status command
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5992 Systemd service provider do not support custom status command Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5926) Service resource ignoring status override.
Title: Message Title Eric Sorenson commented on PUP-5926 Re: Service resource ignoring status override. We linked this ticket to a more specific one about systemd, PUP-5992, which has a pull request up. I'm going to make this ticket more specifically about launchd since that is what your examples show, and it's not covered by the other PR. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5967) File type links documentation incorrectly references :ignore value
Title: Message Title Michael Smith updated an issue Puppet / PUP-5967 File type links documentation incorrectly references :ignore value Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5926) Service resource ignoring status override.
Title: Message Title Eric Sorenson commented on PUP-5926 Re: Service resource ignoring status override. This is because each provider needs to implement the command override. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5926) Service resource ignoring status override.
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-5926
Service resource ignoring status override.
Change By:
Eric Sorenson
I'm seeing some odd behaviour when trying to override the status command of a service which seems to be being ignored.According to the docs, setting {{ hasstatus }} to {{ false }} and adding a custom command to the {{ status }} attribute should allow me to fine tune how Puppet tries to determine if my service is running...{quote}If a service’s init script does not support any kind of status command, you should set hasstatus to false and either provide a specific command using the status attribute or expect that Puppet will look for the service name in the process table.{quote}and for {{ status }}...{quote}Specify a status command manually. This command must return 0 if the service is running and a nonzero value otherwise.{quote}I've boiled my problem down to the following example code{code}service { 'fake_service': ensure=> running, start => '/bin/echo start command', status=> '/bin/true', hasstatus => false,{code}The behaviour I would expect from this is that when evaluating the service, puppet will run {{ /bin/true }} to determine if the service is up, which will return 0, and then stop there since the service should always be deemed running. However when I run the above code I see that the status command is never run and puppet insists on querying the service through systemctl{code}Debug: Executing '/usr/bin/systemctl is-active fake_service'Debug: Executing '/bin/echo start command'Notice: /Stage[main]/Main/Service[fake_service]/ensure: ensure changed 'stopped' to 'running'{code}So far I've seen this on Puppet 4.3.1 (MacOS) and Puppet 3.8.4 (Redhat 7.1)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5920) Implement pluginsync of external facts without using source_permissions
Title: Message Title Michael Smith commented on PUP-5920 Re: Implement pluginsync of external facts without using source_permissions In a world of git, the only permission that makes sense is the executable bit. A replacement for source_permissions would be a more restricted parameter about whether to use the executable bit from the source. That would also suffice for the facts pluginsync use-case. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Henrik Lindberg commented on PUP-5995 Re: Stray UTF-8 character in manifest corrupts parsed parameters I found the problem. It is the SourcePosAdapter methods extract_text and extract_tree_text that are wrong now that UTF-8 encoding is enforced when reading the source. It would have been wrong earlier as well if the default encoding was UTF-8. (This may explain oddities in Puppet Strings with problems not being reproducible). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5913) Detected resources in parsedfile provider can ignore duplicates
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5913 Detected resources in parsedfile provider can ignore duplicates Change By: Steve Barlow Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Steve Barlow assigned an issue to Eric Sorenson Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Steve Barlow Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Eric Sorenson updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Eric Sorenson Fix Version/s: FACT 3.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Steve Barlow commented on PUP-5288 Re: acceptance: puppet ruby in windows should use the correct ssldir Eric Thompson Should this land on the windows scrum team, or is it better on client? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5288 acceptance: puppet ruby in windows should use the correct ssldir Change By: Steve Barlow Sprint: Client 2016-03-23 (Bug Fixes) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5998) [Spike] Rehabilitate Groups
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5998 [Spike] Rehabilitate Groups Change By: Steve Barlow Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-598) local groups should be modified irrespective of users being in LDAP
Title: Message Title Steve Barlow updated an issue Puppet / PUP-598 local groups should be modified irrespective of users being in LDAP Change By: Steve Barlow Sprint: Client 2016-04-10 (C++) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5999) Rehabilitate Groups
Title: Message Title Steve Barlow created an issue Puppet / PUP-5999 Rehabilitate Groups Issue Type: Epic Assignee: Unassigned Created: 2016/03/02 3:32 PM Priority: Normal Reporter: Steve Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5998) [Spike] Rehabilitate Groups
Title: Message Title Steve Barlow created an issue Puppet / PUP-5998 [Spike] Rehabilitate Groups Issue Type: Task Assignee: Unassigned Created: 2016/03/02 3:31 PM Priority: Normal Reporter: Steve Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-598) local groups should be modified irrespective of users being in LDAP
Title: Message Title Steve Barlow updated an issue Puppet / PUP-598 local groups should be modified irrespective of users being in LDAP Change By: Steve Barlow Sprint: Client 2016- 03 04 - 23 10 ( Bug Fixes C++ ) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Steve Barlow updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Steve Barlow Sprint: Client 2016-03-23 (Bug Fixes) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1345) Solaris automount entries in mountpoint result in huge fact lists
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1345 Solaris automount entries in mountpoint result in huge fact lists Change By: Kylo Ginsberg Security: Internal Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5995) Stray UTF-8 character in manifest corrupts parsed parameters
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5995 Stray UTF-8 character in manifest corrupts parsed parameters Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Michael Smith updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Michael Smith Fix Version/s: FACT 3.1.6 Fix Version/s: FACT 3.1.5 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1352) Use Leatherman 0.4.1
Title: Message Title Michael Smith updated an issue Facter / FACT-1352 Use Leatherman 0.4.1 Change By: Michael Smith Fix Version/s: FACT 3.1.6 Fix Version/s: FACT 3.1.5 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1341) Facter Throws Unhandled Exception when Run Under Unicode User
Title: Message Title Michael Smith updated an issue Facter / FACT-1341 Facter Throws Unhandled Exception when Run Under Unicode User Change By: Michael Smith Fix Version/s: FACT 3.1.6 Fix Version/s: FACT 3.1.5 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1352) Use Leatherman 0.4.1
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-1352 Use Leatherman 0.4.1 Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1352) Use Leatherman 0.4.1
Title: Message Title Michael Smith updated an issue Facter / FACT-1352 Use Leatherman 0.4.1 Change By: Michael Smith Summary: Use Leatherman 0.4. 0 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1357) puppet-agent build fails on facter unit test if bundle is installed
Title: Message Title Michael Smith commented on FACT-1357 Re: puppet-agent build fails on facter unit test if bundle is installed The way we handle rspec is messy and requires manual setup. This causes packaging to fail if trying to do a local packaging build. We could do bundle setup in the project bin directory as part of make test, and use it to run specs; or separate rspec out of make test, and require multiple manual steps. This could also be fixed by running bundle install before make test in puppet-agent. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1355) Fix build isolation for generated files
Title: Message Title Michael Smith updated an issue Facter / FACT-1355 Fix build isolation for generated files Change By: Michael Smith Currently generated files are put into the source tree. This makes it impossible to have multiple project directories at once. We should put them all in the project bin directory. Also, the way we handle rspec is messy and requires manual setup. This causes packaging to fail if trying to do a local packaging build. We should do bundle setup in the project bin directory as part of make test, and use it to run specs. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-22) Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation
Title: Message Title Henrik Lindberg commented on NPUP-22 Re: Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation There are three settings that I know of that relates to parsing: The --strict option (off, warning, error) added in 4.5.0 may be one to add to control how to handle "deprecations" There is also the "disabled deprecation warnings" (have to search its actual name) which lets individual deprecations be turned off. Puppet has --strict_variables that has behavior that is in combination with the --strict flag. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5982) Acceptance: add test case for 'parser validate'
Title: Message Title John Duarte updated an issue Puppet / PUP-5982 Acceptance: add test case for 'parser validate' Change By: John Duarte Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5982) Acceptance: add test case for 'parser validate'
Title: Message Title John Duarte updated an issue Puppet / PUP-5982 Acceptance: add test case for 'parser validate' Change By: John Duarte Sprint: QA 2016-03-23 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5986) Bad error for unresolved type in 4.x function API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5986 Bad error for unresolved type in 4.x function API Change By: Henrik Lindberg Sprint: Language Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5982) Acceptance: add test case for 'parser validate'
Title: Message Title John Duarte updated an issue Puppet / PUP-5982 Acceptance: add test case for 'parser validate' Change By: John Duarte Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5855) Deprecate inexact resource reference matches
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5855 Deprecate inexact resource reference matches Change By: Henrik Lindberg Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5810) Increase performance by adding tail-call functionality to evaluator
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5810 Increase performance by adding tail-call functionality to evaluator Change By: Henrik Lindberg Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-23) Recurse on symbolic directory links when searching for files
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-23
Recurse on symbolic directory links when searching for files
Change By:
Peter Huene
For the parse command and when searching for manifests when an environment's {{manifest}} setting is a directory, we need to recurse on symlinks to directories.Boost defaults to not recursing on directory symlinks, so currently they are being ignored by the native compiler.However, when we do add support for this, we need to detect directory symlinks and ensure the link can be read; if it errors (likely returning ELOOP), it means that we can doesn 't safely recurse on the symlink cause a loop .
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-24) Environment manifest setting, when a directory, is not recursing on subdirectories
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-24 Environment manifest setting, when a directory, is not recursing on subdirectories Issue Type: Bug Assignee: Unassigned Created: 2016/03/02 12:23 PM Priority: Normal Reporter: Peter Huene If an environment's manifest setting points at a directory, the native compiler is not recursing to find main manifests. The recursion needs to be done in the currently performed sort-order to make the traversal order predictable. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (NPUP-23) Recurse on symbolic directory links when searching for files
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-23 Recurse on symbolic directory links when searching for files Issue Type: Bug Assignee: Unassigned Created: 2016/03/02 12:19 PM Priority: Normal Reporter: Peter Huene For the parse command and when searching for manifests when an environment's manifest setting is a directory, we need to recurse on symlinks to directories. Boost defaults to not recursing on directory symlinks, so currently they are being ignored by the native compiler. However, when we do add support for this, we need to detect directory symlinks and ensure the link can be read; if it errors (likely returning ELOOP), it means that we can't safely recurse on the symlink. Add Comment
Jira (NPUP-22) Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-22
Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation
Change By:
Peter Huene
!http://i.imgur.com/WY031rI.jpg!The native compiler needs to surface a logical subset of settings in the {{settings}} class and those expected to be set as top-level variables (such as {{environment}}).Right now we have:{code}settings::basemodulepathsettings::codedirsettings::environmentsettings::environmentpathsettings::manifestsettings::modulepath{code}These are settings the native compiler currently respects from the command line and environment . conf where relevant. More may be needed to minimize breaking code depending on these variables. The native compiler should also use defaults from puppet.conf.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-22) Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-22
Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation
Change By:
Peter Huene
!http://i.imgur.com/WY031rI.jpg!The native compiler needs to surface a logical subset of settings in the {{settings}} class and those expected to be set as top-level variables (such as {{environment}}).Right now we have:{code}settings::basemodulepathsettings::codedirsettings::environmentsettings::environmentpathsettings::manifestsettings::modulepath{code}These are settings the native compiler current currently respects. More may be needed to minimize breaking code depending on these variables.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-22) Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-22 Ensure settings and top-level variables match (to a logical extent) those set by the Ruby implementation Change By: Peter Huene Summary: Ensure $ settings and top-level variables match (to a logical extent) those set by the Ruby implementation Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-22) Ensure $settings and top-level variables match (to a logical extent) those set by the Ruby implementation
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-22 Ensure $settings and top-level variables match (to a logical extent) those set by the Ruby implementation Issue Type: Bug Assignee: Unassigned Created: 2016/03/02 11:49 AM Priority: Normal Reporter: Peter Huene The native compiler needs to surface a logical subset of settings in the settings class and those expected to be set as top-level variables (such as environment). Right now we have: settings::basemodulepath settings::codedir settings::environment settings::environmentpath
Jira (PUP-5341) Tag fields in reports accidentally changed to Puppet::Util::TagSet objects
Title: Message Title Michael Smith commented on PUP-5341 Re: Tag fields in reports accidentally changed to Puppet::Util::TagSet objects Verified with an agent run using the PR, and looking at last_run_report. It now serializes tags as an array rather than a TagSet. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-501) {{%{literal(...)\}}} can appear only once in any data value
Title: Message Title
Johnson Earls created an issue
Hiera / HI-501
{{%{literal(...)\}}} can appear only once in any data value
Issue Type:
Bug
Affects Versions:
HI 3.0.1
Assignee:
Jenny Mahmoudi
Components:
UX
Created:
2016/03/02 11:43 AM
Priority:
Normal
Reporter:
Johnson Earls
Multiple
identical
calls to the Hiera lookup function %{literal()} in the same Hiera data key cause an error. This includes when the %{hiera()} or %{alias()} lookup functions are called and the included keys contain identical %{literal()} calls. However, it
works
when using %{hiera()} to include two
different
Hiera keys that contain identical %{literal()} calls.
Jira (FACT-1352) Use Leatherman 0.4.0
Title: Message Title Michael Smith updated an issue Facter / FACT-1352 Use Leatherman 0.4.0 Change By: Michael Smith Comment: Blocked on Facter release Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title Henrik Lindberg commented on PUP-5971 Re: Define evaluation should be evaluated depth-first, not breadth-first Hunter Haugen yep, things like what you describe makes it difficult. What I think we need to do is to also merge the desires of different expressions. Still makes it hard as the meaning of an include (which will lookup defaults for parameters via data binding) may be different than what is stated in the manifests. We need precedence rules to determine which value wins. I think we need to consider that anyway to allow the same parameterized class to be declared more than once, to be able to have sane default attribute expressions, (and a couple of other use cases). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Eric Sorenson updated an issue
Facter / FACT-1356
External facts should be able to return structured data
Change By:
Eric Sorenson
Currently, external facts can only return simple key=value. For consistency with the rest of the ecosystem, external facts should be able to be structured.Seems like it'd be workable to support either key=value or json by looking for an opening {{\{}} curly brace to indicate JSON.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Eric Sorenson updated an issue
Facter / FACT-1356
External facts should be able to return structured data
Change By:
Eric Sorenson
Currently, external facts can only return simple key=value. For consistency with the rest of the ecosystem, external facts should be able to be structured.Seems like it'd be workable to support either key=value or json by looking for an opening {{ \ {}} to indicate JSON.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Eric Sorenson updated an issue
Facter / FACT-1356
External facts should be able to return structured data
Change By:
Eric Sorenson
Currently, external facts can only return simple key=value. For consistency with the rest of the ecosystem, external facts should be able to be structured.Seems like it'd be workable to support either key=value or json by looking for an opening {{ a { }} to indicate JSON.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Eric Sorenson updated an issue
Facter / FACT-1356
External facts should be able to return structured data
Change By:
Eric Sorenson
Currently, external facts can only return simple key=value. For consistency with the rest of the ecosystem, external facts should be able to be structured.Seems like it'd be workable to support either key=value or json by looking for an opening {{ a }} to indicate JSON.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Eric Sorenson updated an issue
Facter / FACT-1356
External facts should be able to return structured data
Change By:
Eric Sorenson
Currently, external facts can only return simple key=value. For consistency with the rest of the ecosystem, external facts should be able to be structured.Seems like it'd be workable to support either key=value or json by looking for an opening {{ { a }} to indicate JSON.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Eric Sorenson updated an issue
Facter / FACT-1356
External facts should be able to return structured data
Change By:
Eric Sorenson
Currently, external facts can only return simple key=value. For consistency with the rest of the ecosystem, external facts should be able to be structured.Seems like it'd be workable to support either key=value or json by looking for an opening {{ \ {}} to indicate JSON.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5866) Static catalog acceptance: Per environment control of static catalog, Story PUP-5705
Title: Message Title Kurt Wall updated an issue Puppet / PUP-5866 Static catalog acceptance: Per environment control of static catalog, Story PUP-5705 Change By: Kurt Wall Attachment: puppetserver.log Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title Henrik Lindberg commented on PUP-5971 Re: Define evaluation should be evaluated depth-first, not breadth-first That is not what I meant - rather a forked compiler that could be tried when using a git branch - if it is not horrible it could be introduced behind a feature switch. The catalog preview could compare two compilations regular compiler, new "depth first" compiler. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5866) Static catalog acceptance: Per environment control of static catalog, Story PUP-5705
Title: Message Title
Kurt Wall commented on PUP-5866
Re: Static catalog acceptance: Per environment control of static catalog, Story PUP-5705
I think this test leaves state behind on the server that causes subsequent runs to break if not using the production environment. The actual error is:
Caused by: org.jruby.embed.InvokeFailedException: (EnvironmentNotFound) Could not find a directory environment named 'fantasy' anywhere in the path: /tmp/static_catalog_env_control.rb.6PkssD/code/environments. Does the directory exist?
at org.jruby.embed.internal.EmbedRubyObjectAdapterImpl.call(EmbedRubyObjectAdapterImpl.java:317) ~[puppet-server-release.jar:na]
To repro:
Set up master and standalone agent (I used the vmpooler setup and pre-suite)
Run this test
On the master, manually create a fantasy env: mkdir -p $codedir/environments/fantasy/{manifests,modules}
Edit puppet.conf, setting environment = fantasy in the [main] section
Tail the puppetserver log
Run {{puppet agent --test --server SERVER }}
See the error in the attached puppetserver.log
Edit puppet.conf, setting environment = production in the [main] section
See the run complete successfully
Jira (FACT-1357) puppet-agent build fails on facter unit test if bundle is installed
Title: Message Title Michael Smith assigned an issue to Unassigned Facter / FACT-1357 puppet-agent build fails on facter unit test if bundle is installed Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
