Jira (PUP-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title
Kris Bosland updated an issue
Puppet / PUP-6344
metrics.time.total does not correlate to time reported in log
Change By:
Kris Bosland
Acceptance Criteria:
The {{total}} time should represent the amount of time spent by the agent between waking up to start a run and submitting the report at the end of the run.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Alex Dreyer Assignee: Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7533) User resource in AIX does not update attributes
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7533 User resource in AIX does not update attributes Change By: Owen Rodabaugh CS Priority: Needs Priority Minor CS Impact: For AIX customers who use the user attribute this is very frustrating and requires them to workaround it via exec. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-452) Docs don't say what's required to start using Bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-452 Docs don't say what's required to start using Bolt Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-452) Docs don't say what's required to start using Bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-452 Docs don't say what's required to start using Bolt Change By: Michael Smith Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8257) Puppet::FileSystem::Windows should support LFN
Title: Message Title Ethan Brown commented on PUP-8257 Re: Puppet::FileSystem::Windows should support LFN If we want to land this in Puppet::FileSystem it might make sense to add to the epic PUP-7557 As much as I hate the idea, this might need to be one place where we monkey-patch Ruby classes to fix broken functionality, because there's a number of 3rd party locations (like in minitar) where we won't be able to change the original gem code. Food for thought as further work happens here. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-440) Publish bolt orchestrator shim to the Puppet Forge
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-440 Publish bolt orchestrator shim to the Puppet Forge Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-457) Facter PowerShell task relies on method that is not implemented in all versions of .NET
Title: Message Title James Pogran created an issue Puppet Task Runner / BOLT-457 Facter PowerShell task relies on method that is not implemented in all versions of .NET Issue Type: Bug Assignee: Unassigned Created: 2018/04/05 11:56 AM Priority: Normal Reporter: James Pogran https://github.com/puppetlabs/bolt/blob/master/modules/facts/tasks/powershell.ps1 uses System.Environment.OSVersion to determine the OS Version of the target node. As explained in https://github.com/PowerShell/PowerShell/issues/2009, .NET Core did not implement this method correctly because the underlying API it calls isn't cross-platform. There is more detail in https://github.com/dotnet/coreclr/pull/6006, with no clear resolution. The result of this is that in .NET Core, the value is either incorrect or returns an error that it isn't implemented. On Windows 10, running under PowerShell Core, it returns 8.1. Bolt does not use pwsh.exe, it uses powershell.exe, so there is no immediate problem here. However this will be a subtle bug in the future, that won't manifest as an error but as incorrect data instead. Add Comment
Jira (PUP-8498) Improve error for 'No title provided and "foo" is not a valid resource reference'
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8498 Improve error for 'No title provided and "foo" is not a valid resource reference' Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-456) Plans should restrict return types to expected values
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-456
Plans should restrict return types to expected values
Change By:
Alex Dreyer
Currently plans can return pcore objects that cannot be handled outside the compiler. To avoid errors around this we should limit the acceptable return values of plan to the {{Data}} and the datatypes we expect plans to generate, {{Error}}, {{Result}}, {{ResultSet}}, and {{Target}}. As the plan language matures we may broaden this setIf a plan does not return an expected value run_plan should raise a Bolt::InvalidPlanResult value error. { noformat}{ kind: 'bolt/invalid-plan-result', message: "Plan #{plan_name} returned and invalid result of type #{DatatypeName}" details: nil { plan_name: plan_name,type: datatype_name, } } {noformat} We should expose a new type alias {{PlanData}} to match the acceptable return values.{noformat}type PlanData = Variant[Data, Error, Result, ResultSet, Target, Array[PlanData], Hash[String, PlanData]]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-456) Plans should restrict return types to expected values
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-456
Plans should restrict return types to expected values
Change By:
Alex Dreyer
Currently plans can return pcore objects that cannot be handled outside the compiler. To avoid errors around this we should limit the acceptable return values of plan to the {{Data}} and the datatypes we expect plans to generate, {{Error}}, {{Result}}, {{ResultSet}}, and {{Target}}. As the plan language matures we may broaden this setIf a plan does not return an expected value run_plan should raise a Bolt::InvalidPlanResult value error. {noformat}{ kind: 'bolt/invalid-plan-result', message: "Plan #{plan_name} returned and invalid result of type #{ DatatypeName datatype_name }" details: {plan_name: plan_name,type: datatype_name, }}{noformat}We should expose a new type alias {{PlanData}} to match the acceptable return values.{noformat}type PlanData = Variant[Data, Error, Result, ResultSet, Target, Array[PlanData], Hash[String, PlanData]]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-456) Plans should restrict return types to expected values
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-456
Plans should restrict return types to expected values
Change By:
Alex Dreyer
Currently plans can return pcore objects that cannot be handled outside the compiler. To avoid errors around this we should limit the acceptable return values of plan to the {{Data}} and the datatypes we expect plans to generate, {{Error}}, {{Result}}, {{ResultSet}}, and {{Target}}. As the plan language matures we may broaden this setIf a plan does not return an expected value run_plan should raise a Bolt:: InvalidReturn InvalidPlanResult value error. { kind: Bolt 'bolt/invalid-plan-result', message : "Plan #{plan_name} returned and invalid result of type #{DatatypeName}" details : InvalidPlanResult nil } We should expose a new type alias {{PlanData}} to match the acceptable return values.{noformat}type PlanData = Variant[Data, Error, Result, ResultSet, Target, Array[PlanData], Hash[String, PlanData]]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-456) Plans should restrict return types to expected values
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-456
Plans should restrict return types to expected values
Change By:
Alex Dreyer
Currently plans can return values pcore objects that bolt cannot print or handle be handled outside the compiler . To avoid errors around this we should limit the acceptable return values of plan to the {{Data}} and the datatypes we expect plans to generate, {{Error}}, {{Result}}, {{ResultSet}}, and {{Target}}. As the plan language matures we may broaden this set If a plan does not return an expected value run_plan should raise a Bolt::InvalidReturn value error. { kind: Bolt::InvalidPlanResult We should expose a new type alias { {PlanData}} to match the acceptable return values.{ noformat}type PlanReturn PlanData = Variant[Data, Error, Result, ResultSet, Target, Array[ PlanReturn PlanData ], Hash[String, PlanReturn PlanData ]]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message
Jira (BOLT-456) Plans should restrict return types to expected values
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-456
Plans should restrict return types to expected values
Change By:
Alex Dreyer
Currently plans can return values that bolt cannot print to or handle. { { noformat} } type PlanReturn = Variant[Data, Error, Result, ResultSet, Target, Array[PlanReturn], Hash[String, PlanReturn]]{ { noformat} }
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 (BOLT-456) Plans should restrict return types to expected values
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-456
Plans should restrict return types to expected values
Change By:
Alex Dreyer
Currently to_json on the plan calls to_s which calls into the pcore string converter. Outside the context of the compiler this is infinitely recursive.Since we expect plans to can return the Error datatype and values that bolt displays plans by calling to_json on the result the Error datatype needs cannot print to support to_json. The to_json method should return the jsonified hash representation. {{noformat}}type PlanReturn = Variant[Data, Error, Result, ResultSet, Target, Array[PlanReturn], Hash[String, PlanReturn]]{{noformat}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 thi
Jira (BOLT-456) Error datatype should support to_json
Title: Message Title Alex Dreyer moved an issue Puppet Task Runner / BOLT-456 Error datatype should support to_json Change By: Alex Dreyer Key: PUP BOLT - 8441 456 Project: Puppet Task Runner Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-456) Plans should restrict return types to expected values
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-456 Plans should restrict return types to expected values Change By: Alex Dreyer Summary: Error datatype Plans should support to_json restrict return types to expected values Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-599) Hiera cannot interpolate non-string values
Title: Message Title
Trevor Vaughan commented on HI-599
Re: Hiera cannot interpolate non-string values
It would be ideal if, instead of overriding particular lookups at the configuration layer, that this could be exposed at interpolation time so that it is less confusing for users. For instance, something like the following would be nice: "%{typed('facts.selinux.enabled', 'Boolean')}"
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 (BOLT-370) file_upload() function docs should have a caveat for transferring large files
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-370 file_upload() function docs should have a caveat for transferring large files Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Alex Dreyer Since we can log intermediate results and error on failure returning the entirety of the last line often clutters and obscures meaningful output. Some users have reported returning static strings to prevent this. Plans that called from other plans may expose an unintentional and unstable API due to this as well.Solution:The result of a plan should be undef unless there is an explicit return statement in the plan.Questions:Is it useful in simple plans to return the last value? No, simple plans can rely on logging and default error handling.Is this too much of a differentiation from puppet functions? No, Plans are not functions and are usually run for side effects whereas functions are usually run for their return value in the plan language. Making this difference explicit makes it's clearer to users when to write a sub-plan vs a dsl function. Additional Scope:When the result of a plan is undef the human output format should print:"Plan completed successfully with no result" instead of null Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Yasmin Rajabi Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-440) Publish bolt orchestrator shim to the Puppet Forge
Title: Message Title Yasmin Rajabi assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-440 Publish bolt orchestrator shim to the Puppet Forge Change By: Yasmin Rajabi Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-370) file_upload() function docs should have a caveat for transferring large files
Title: Message Title Yasmin Rajabi assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-370 file_upload() function docs should have a caveat for transferring large files Change By: Yasmin Rajabi Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8441) Error datatype should support to_json
Title: Message Title Yasmin Rajabi assigned an issue to Unassigned Puppet / PUP-8441 Error datatype should support to_json Change By: Yasmin Rajabi Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-452) Docs don't say what's required to start using Bolt
Title: Message Title Michael Smith commented on BOLT-452 Re: Docs don't say what's required to start using Bolt I thought the hands-on-lab noted you can use --no-host-key-check to log into machines you haven't added to your known hosts. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-599) Hiera cannot interpolate non-string values
Title: Message Title
Carl Caum created an issue
Hiera / HI-599
Hiera cannot interpolate non-string values
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/04/05 8:43 AM
Priority:
Normal
Reporter:
Carl Caum
It is not possible for Hiera to interpolate non-string values from Facter. For example, the `selinux.enabled` fact has a Boolean value. However, in Hiera you cannot do something like:
docker::selinux_enabled: %{facts.selinux.enabled}
Instead, the user has to quote the facter fact code so it can be interpolated, like this:
docker::selinux_enabled: "%{facts.selinux.enabled}"
which inadvertently casts any non-string values to a string. Example of a user experiencing this problem: https://github.com/puppetlabs/puppetlabs-docker/issues/212
Jira (BOLT-455) Puppets log format doesn't match bolts
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-455 Puppets log format doesn't match bolts Issue Type: Bug Assignee: Unassigned Created: 2018/04/05 8:20 AM Priority: Normal Reporter: Alex Dreyer The puppet logger format doesn't match bolt's which makes is difficult to read logs that intermingle messages generated by bolt and messages logged intentionally from the the plan. Ideally users would be able to use the normal puppet log functions from their plans and have the format match bolt's log messages and get sent to the same destinations. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8633) Node agents connecting to specific Complie master
Title: Message Title Mohammed created an issue Puppet / PUP-8633 Node agents connecting to specific Complie master Issue Type: Bug Affects Versions: PUP 5.5.0 Assignee: Unassigned Components: Puppet Server Created: 2018/04/05 7:37 AM Fix Versions: None Priority: Critical Reporter: Mohammed Puppet Version: 5.5 Puppet Server Version: 2017 v3.2** OS Name/Version: Centos version 7 Hello, We have puppet enterprise running in our environment , we have three complie masters which talks to MoM. every complie master is residing in islolated envrionment. now the concern is how can i point agents to talk to their Complie master from the start of agent installation on a new machine when provisioned in a environment. Desired Behavior: how can i point agents to talk to their Complie master from the start of agent installation on a new machine when provisioned in a environment. Actual Behavior: now when i install puppet agent, it tries to reach all the three complie masters which is not right for cert sign and installation.
Jira (PUP-7307) Tidy should support 'purge' or update file resource
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-4678) Enable yumrepo priority attribute to support lower priority than 99
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-4678 Enable yumrepo priority attribute to support lower priority than 99 Change By: Eric Delaney Assignee: Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8421) Add error handing to Yum provider
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8421 Add error handing to Yum provider Change By: Eric Delaney Assignee: Jennifer Solman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8514) Puppet should have a way of defining properties or parameters for types as sensitive
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8514 Puppet should have a way of defining properties or parameters for types as sensitive Change By: Eric Delaney Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8632) Puppet Device --apply fails to apply catalog to unregistered targets
Title: Message Title David Armstrong created an issue Puppet / PUP-8632 Puppet Device --apply fails to apply catalog to unregistered targets Issue Type: Improvement Assignee: Thomas Honey Created: 2018/04/05 3:55 AM Priority: Normal Reporter: David Armstrong Having created a new provider and wishing to apply a manifest to my new target: bundle exec puppet device --verbose --trace --modulepath ~/projects --target=hue_hub --deviceconfig /Users/david.armstrong/test_manifests/device.conf --apply ~/test_manifests/hue_disco.pp returns Notice: Compiled catalog for hue_hub in environment production in 0.09 seconds Info: Applying configuration version '1522924613' Info: Creating state file /Users/david.armstrong/.puppetlabs/opt/puppet/cache/devices/hue_hub/state/state.yaml
Jira (BOLT-439) Allow nested subgroups in inventory files
Title: Message Title Michal Ruzicka assigned an issue to Michal Ruzicka Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: Michal Ruzicka Assignee: Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg commented on PUP-8240 Re: ERB and EPP templates handle CRLF line endings inconsistently AppVeyor fails miserably in what seems unrelated to this change. Help needed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-598) Hiera ruby gem not supporting hiera v5 yaml file.
Title: Message Title Henrik Lindberg commented on HI-598 Re: Hiera ruby gem not supporting hiera v5 yaml file. The hiera gem is only for hiera 3. Hiera 5 is completely in Puppet. Hiera 3 is also deprecated and support for it will at some point be dropped along with the hiera gem. The problem is in rspec-puppet as it seems to think it can give a hiera.yaml directly to the hiera gem. That is not true as it needs puppet to deal with the hiera.yaml file, not the deprecated hiera 3 gem (which is only used by hiera 5 as a supporting library for hiera 3 backends). The issue should be reported against rspec-puppet. Ping Tim Sharpe. I am closing this as a won't do as there is nothing we can do about the problem in the hiera 3 implementation. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
