r10k continuously updating elastic_stack about puppet-elastic_stack HOT 7 CLOSED

Is this because the forge package has the .git config included in it?
My setup is trying to initialise it as a git submodule because of this which leaves the deployed elastic_stack directory empty on my puppet servers.

from puppet-elastic_stack.

My elastic_stack directory wasn't coming up empty -- but it was being deleted and recreated over and over. =) (which meant that the unluckily timed clients would error out since they were not able to find the module) I hadn't noticed the git config before though! I bet that has something to do with it and maybe we have different (something) versions that is causing you to have an empty directory where I don't.

from puppet-elastic_stack.

I'm not using r10k on my production system just a monolithic Git repo, but I can test if I get the same result as you with r10k.
What r10k command do you use to deploy?

from puppet-elastic_stack.

I use: r10k deploy environment -pv
(with an appropriately set up control repo and Puppetfile -- most important part of the Puppetfile being:
mod 'elastic/elastic_stack', '6.2.4'

from puppet-elastic_stack.

Oh yeah -- and an r10k.yaml of:

---
:postrun: ["/usr/local/sbin/r10k_postrun.sh"]
:cachedir: /opt/puppetlabs/puppet/cache/r10k
:sources:
  chass:
    basedir: /etc/puppetlabs/code/environments
    prefix: true
    remote: MY_GIT_REPO

:deploy:
  purge_whitelist:
  - ".resource_types"
  - ".resource_types/**"

:git:
  private_key: "/etc/pki/git/github"
  provider: shellgit
  username: MY_GIT_USERNAME

from puppet-elastic_stack.

This is definitely because the release tarball for 6.2.4 contains a local .git directory, as @matt-cahill noticed. This confuses r10k, especially when running r10k deploy environment -p.

from puppet-elastic_stack.

Can confirm this is fixed in 6.3.1. Closing issue.

from puppet-elastic_stack.