Jira (FACT-1441) Add "cloud" fact that identifies Azure
Title: Message Title Scott McClellan assigned an issue to Unassigned Facter / FACT-1441 Add "cloud" fact that identifies Azure Change By: Scott McClellan Assignee: Scott McClellan Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6984) alias on Package/Exec resources produces misleading warning
Title: Message Title Sven Mueller commented on PUP-6984 Re: alias on Package/Exec resources produces misleading warning After reading a bit more, I'm unconvinced that the check from PUP-5855 is actually helpful, unless auto-generated resources (like the file provider can create, IIUC - I never really used that, instead making each dependency and stage of directory creations explicit) are also deprecated. In any case, not allowing explicit aliased makes the language feature unusable. Do you intend to mark that metaparameter as deprecated? And many style guides I came across said to use actual pathnames in File resources (and more generally: Don't use the attribute tagged as namevar, unless you have very good reason to do so. I'm not sure your quest to only refer to resources by their title is such a good reason. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6984) alias on Package/Exec resources produces misleading warning
Title: Message Title
Sven Mueller commented on PUP-6984
Re: alias on Package/Exec resources produces misleading warning
If you only allow referencing the resources by their title, the alias metaparameter looses its meaning completely. And while I don't know current training material, it was provided in the past as "the" way to allow interoperability while keeping manifests readable/meaningful.
Consider this:
package {'apache2': ensure => present, alias => 'http-server', }
vs.
package {'http-server': ensure => present, name => 'apache2' }
When installation of the package fails, the first tells you which package failed to install (apache2), while the second will tell you a symbolic name (and later on the command, but this also gets confusing).
I agree that the server should warn about undefined resources.
But a resource definition with an alias should define one resource with two names, so this bug is not about a misleading warning in the end, but about an oversight in the change that was merged at 668fef0: It should not just look at resource titles, but also at their aliases.
I'm not sure if unless catalog.resource(r.to_s) should be replaced with something else, or if catalog.resource() is incorrect here and should also return resources by alias.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command.See REPRO REPROs in comment below.For example, if you have an environment called 'dev' on the master, and you want to set an agent's $environment from the default of 'production' to 'dev', you might issue a {{puppet config set environment dev}} comand. When run, {{puppet config}} will look up the current environment ('production' at this point) and ensure there is a corresponding 'production' folder in the environments path. Assume this succeeds because a 'production' folder exists locally on the agent, by default, but NO OTHER environment folders exist locally on the agent (and shouldn't need to exist in my view).Now the environment is set to 'dev'.If a user issues any {{puppet config}} command at this point, the current environment ('dev' at this point) will NOT have a corresponding environment folder, so we get an error like:{code}Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?{code}{code}[root@pup-vra7-0403 ~]# puppet config set environment production/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `'{code}This means we're stuck and cannot issue any {{puppet config print}} or {{puppet config set}} commands even to get us back to an environment setting of 'production'!
Add Comment
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command.See REPROs in comment comments below.For example, if you have an environment called 'dev' on the master, and you want to set an agent's $environment from the default of 'production' to 'dev', you might issue a {{puppet config set environment dev}} comand. When run, {{puppet config}} will look up the current environment ('production' at this point) and ensure there is a corresponding 'production' folder in the environments path. Assume this succeeds because a 'production' folder exists locally on the agent, by default, but NO OTHER environment folders exist locally on the agent (and shouldn't need to exist in my view).Now the environment is set to 'dev'.If a user issues any {{puppet config}} command at this point, the current environment ('dev' at this point) will NOT have a corresponding environment folder, so we get an error like:{code}Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?{code}{code}[root@pup-vra7-0403 ~]# puppet config set environment production/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `'{code}This means we're stuck and cannot issue any {{puppet config print}} or {{puppet config set}} commands even to get us back to an environment setting of 'production'!
Add Comment
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command.See REPRO in comment below.For example, if you have an environment called 'dev' on the master, and you want to set an agent's $environment from the default of 'production' to 'dev', you might issue a {{puppet config set environment dev}} comand. When run, {{puppet config}} will look up the current environment ('production' at this point) and ensure there is a corresponding 'production' folder in the environments path. Assume this succeeds because a 'production' folder exists locally on the agent, by default, but NO OTHER environment folders exist locally on the agent (and shouldn't need to exist in my view).Now the environment is set to 'dev'.If a user issues any {{puppet config}} command at this point, the current environment ('dev' at this point) will NOT have a corresponding environment folder, so we get an error like:{code}Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?{code}{code}[root@pup-vra7-0403 ~]# puppet config set environment production/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `'{code}This means we're stuck and cannot issue any {{puppet config print}} or {{puppet config set}} commands even to get us back to an environment setting of 'production'!
Add Comment
Jira (PUP-6781) support 'verbatim' lookup option
Title: Message Title Thomas Hallgren commented on PUP-6781 Re: support 'verbatim' lookup option There was no unit test for this new behavior so I added one. That, of course, revealed a bug so I fixed it and created a PR. I reverted the status of this ticket back to "Ready for merge" Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6781) support 'verbatim' lookup option
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6781 support 'verbatim' lookup option Change By: Thomas Hallgren Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6781) support 'verbatim' lookup option
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6781
support 'verbatim' lookup option
Change By:
Henrik Lindberg
Release Notes Summary:
The hiera meta data {{lookup_options}} now supports that a key can be set to {{verbatim : true}} in order to prevent interpolation from taking place. This is helpful when a data value should contain %\{\} values as it avoids having to escape each such occurrence in the value.
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-6781) support 'verbatim' lookup option
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6781 support 'verbatim' lookup option Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
