Oh excellent. Thanks for reverting. I may see if I can spend some time
or it if only to write more complete tests so it doesn't flip flop in
the future.
Ramin
On 8/18/16 8:37 PM, Rob Nelson wrote:
Ramin,
No worries, it's a legitimate complaint. Puppet-lint 2.0.2 was just
released which rever
Hi
Think you missed my point. in my example I want to limit where the updates
go.
Presumably the puppet agent is set to some periodic period. I believe
30min.
so when i push my test case, say using the puppet --environment command,
30min later it will be updated back.
A
On Friday, 19 Augu
Ramin,
No worries, it's a legitimate complaint. Puppet-lint 2.0.2 was just
released which reverted that issue. We're back to the original problem in
#504 but it's not worse than it was in 2.0.0 at least.
Rob Nelson
rnels...@gmail.com
On Thu, Aug 18, 2016 at 9:56 PM, Ramin K wrote:
> On 8/18/1
The number of branches you have has almost nothing to do with how fast your
nodes converge to a new desired state. If you want them to check in on
command, use mcollective or another orchestration engine to make that
happen.
On Thursday, August 18, 2016, Alex Samad wrote:
> Hi
>
> I have recentl
On 8/18/16 9:35 AM, Rob Nelson wrote:
All,
I'm happy to announce that puppet-lint 2.0.1 has been released today.
Please checkout the changelog below for details. Please open a ticket on
the project if you discover any issues with it.
This is the second release of puppet-lint this year and we ho
Found this
additional_includes
On Friday, 19 August 2016 10:39:07 UTC+10, Alex Samad wrote:
>
> Hi
>
> How to I set this
>
>
>Options -Indexes
>
>
> # x-frame
> Header always append X-Frame-Options SAMEORIGIN
>
> But I want to do it outside of the vhost config, so its the default for
Hi
I have recently gone through this problem.
I had initial thought to you different branches for the different
environments.
say
prod
uat
sim
inf
dev
But was advised best to go with production and testing.
so I have and I have used a grouping in my ENC to put machines into the
above groups
Hi
How to I set this
Options -Indexes
# x-frame
Header always append X-Frame-Options SAMEORIGIN
But I want to do it outside of the vhost config, so its the default for all
vhosts ?
And/or how can I do the DirectoryMatch inside a vhost - there isn't an
example in the readme.
Alex
--
Can you check the value of 'environment_timeout' in your puppet.conf and/or
environment.conf files? If that is set to anything other than zero, this
might be expected behavior. There is an HTTP API that you can use to clear
the environment cache if you need to:
https://docs.puppet.com/puppets
At rate any, yes, that running "yum update puppetserver" followed by "yum
downgrade puppetserver-2.4.0-1.el7" without any other precautions may hose
the CRL seems like it deserves mention.
On Thu, Aug 18, 2016 at 2:08 PM, Jeremy Barlow
wrote:
>
> On Thursday, August 18, 2016 at 9:53:37 AM UTC-7,
On Thursday, August 18, 2016 at 9:53:37 AM UTC-7, Ben West wrote:
>
> The configuration for running Open Source puppetserver with an external CA
> changed in v2.4 -> v2.5, explained in more detail here:
>
> https://docs.puppet.com/puppetserver/latest/bootstrap_upgrade_notes.html#cacfg
>
> If you
restarted pe-puppetserver seems to clear cache on master, and the node got
the updated version. But if I make any other changes to my modules, node
isnt getting the updated catalog, its using cached version again.
Master running on Ubuntu 14.04 puppet 4.5.2
node running on centos7 puppet 4.5.2
The configuration for running Open Source puppetserver with an external CA
changed in v2.4 -> v2.5, explained in more detail here:
https://docs.puppet.com/puppetserver/latest/bootstrap_upgrade_notes.html#cacfg
If you happen to run yum upgrade (presumably similar results with apt-get
update), the
All,
I'm happy to announce that puppet-lint 2.0.1 has been released today.
Please checkout the changelog below for details. Please open a ticket on
the project if you discover any issues with it.
This is the second release of puppet-lint this year and we hope to keep the
pace up in the coming mon
Puppet 4.5.2
On Thursday, August 18, 2016 at 12:32:12 PM UTC-4, mike r wrote:
>
> Im trying to run an Nginx module, my install.pp has the following line
>
>
>
> $agent_version = $::puppetversion
>
> # if $agent_version < 3.8 {
> #fail(" Node ${::fqdn} has a Puppet agent version:
> $
Im trying to run an Nginx module, my install.pp has the following line
$agent_version = $::puppetversion
# if $agent_version < 3.8 {
#fail(" Node ${::fqdn} has a Puppet agent version: ${agent_version}
which is not compatible with this module. Need to have minimum Puppet
agent 3
The term 'environment' is overloaded. In the context of puppet, I prefer to
think of it as "a set of puppet code/data representing a branch of the
controlrepo' (puppet environment), rather than 'an environment that nodes
run in' (dev/qa/prod/etc) (node environment). Since you can make the latter
pa
The static branches are basically Puppet environments in which nodes are
bound/pointed to them in their puppet.conf. This way we can open CR's per
set of nodes and move up the chain. Also, I may have found another option
on Gary's site. We could r10k our hiera data and split it from our contr
I'm missing why you need static branches. I'm picturing something more like:
git checkout production
git checkout -b ticket1234
# make changes, commit, push, test, repeat
git merge production # catch up on any prod changes, retest
git tag ticket.1234
git checkout production
git merge ticket1234
gi
Rob,
Thanks for your reply. When our ops team makes a change in hieradata to
the dev branch for example, all dev machines (in the dev puppet
environment) will receive the new hiera data (we want this to happen). We
then ask them to merge that up to test, and finally to production. If an
eng
Mike, is there a reason that Puppetfile changes and hiera changes are being
made in sync, when they aren't tied to each other? Perhaps those Puppetfile
changes that are not ready to be merged should be in a branch called
'experimental' (or even a more-persistent-than-normal feature branch) and
only
Thanks for your reply. We based our initial design on shit Gary says.
This may be our only option as you say, to have hiera data changes made to
each static branch/puppet environment by hand and not merge. We need the
static branches for separation of Puppet environments. Problem with this
BTW, that fixed it. Thanks!
On Wednesday, August 17, 2016 at 8:22:03 PM UTC-4, Bret Wortman wrote:
>
> I'd love to figure out how that changed on me, because your changes remind
> me that it USED to look like that!
>
> Bret Wortman
> http://wrapbuddies.co/
>
> On Aug 17, 2016, 8:01 PM -0400, Wy
23 matches
Mail list logo
