My advice would be to open a support ticket and ask for assistance on
verifying the Classifier settings will transfer in an upgrade, as well as
how to back them up. I did experience some issues with it, and in hindsight
it would be have been quicker to export the important settings, install a
new s
Hi David,
Most of this looks fine (I still need to digest some of it) but I don't
know that I'm a huge fan of no munge or validate functionality. This seems
to fly in the face of a 'fail fast' mentality.
Also, if everything happens on the client, some of the catalog munging that
I do on the fly i
Hey Rob! Thanks for the reply. Yes, I am running a monolithic
installation.
So, you believe I can just install 2015.3.3 over the existing, current,
installation? Then again install-in-place with the latest version of PE?
Is there anything you can think of in the installation instructions I
sho
It works. Thanks.
On Saturday, January 28, 2017 at 11:16:27 AM UTC-8, Rob Nelson wrote:
>
> We use Post-Receive Webhook from the marketplace.
>
> On Sat, Jan 28, 2017 at 4:36 AM Bing Shiao > wrote:
>
>> This question is related to Bitbucket Server (Stash).
>>
>> I have pe_code_manager_webhook wor
It might be a good idea to add `puppet parser validate` and puppet-lint to
your pre commit hooks, they should help catch most similar issues.
On Wed, Feb 1, 2017 at 12:26 PM Joshua Schaeffer
wrote:
>
> That should be $color =
>
>
> Wow, I knew it was something simple. I swear I looked at that fo
>
>
> That should be $color =
>
>
Wow, I knew it was something simple. I swear I looked at that for 10
minutes straight and couldn't find the syntax error. Thanks for pointing it
out. I corrected the syntax error and it's all working correctly now.
Thanks,
Joshua
--
You received this messag
Hello,
thank you it works :
apt::source { "jenkins-${lsbdistcodename}":
location => 'http://pkg.jenkins.io/debian-stable',
key => 'A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553',
release => 'binary/',
repos=> '',
note that trailing slash after binary is mandatory for apt.
I think I
Hello,
A small announcement: I recently launched PuppetModule.info, a site that
generates documentation for modules published on Puppet Forge and
GitHub, using Puppet Strings. It includes docs for all classes, defined
types, parameters etc. contained within a module.
http://www.puppetmodule.inf
On 01/02/17 00:20, Joshua Schaeffer wrote:
I'm new to Puppet and learning the program and language so this question
might seem novice. I'm confused why I can assign an escape character to
a variable but not inside any collection types (arrays or hashes). I was
doing the simply motd puppet module
Did you omit the "$" here for the $color hash or is it missing in the
source ?
--
Lowe Schmidt | +46 723 867 157
On 1 February 2017 at 00:20, Joshua Schaeffer
wrote:
> I'm new to Puppet and learning the program and language so this question
> might seem novice. I'm confused why I can assign an
I'm new to Puppet and learning the program and language so this question
might seem novice. I'm confused why I can assign an escape character to a
variable but not inside any collection types (arrays or hashes). I was
doing the simply motd puppet module and I created this:
$red = "^[[0;31m"
$gr
On 30/01/17 22:34, Martin Alfke wrote:
AFAIK all variables inside a lambda are “private”:
https://docs.puppet.com/puppet/latest/lang_lambdas.html#lambda-scope
Correct - they are local and only visible to inner scopes in the lambda
(a lambda in a lambda).
If you need an iterative function to
12 matches
Mail list logo
