k8s: modules do not get deployed per updated Puppetfile

[slconley]

Describe the Bug

When a Puppetfile in any branch of the puppet-control repo is updated to add modules, those modules do not get deployed when r10k-deploy cronjob is run.

Expected Behavior

Modules added to any environment Puppetfile should be deployed to environment directory (i.e. /etc/puppetlabs/code/environments/production/modules).

Steps to Reproduce

Steps to reproduce the behavior:

1. Deploy app as normal, with at least one branch/environment in a puppet-control repo, and that repo having a Puppetfile with some modules listed.
2. Wait for the cronjob to complete the initial r10k deploy, and verify that the modules were deployed for the environment.
3. Add some modules to the Puppetfile for that environment and commit/push to the puppet-control repo.
4. Wait for next run of r10k-deploy cronjob. Verify that no new modules were added to puppetserver container.

Environment

• Version: Kubernetes 1.14.8
• Platform: Docker-for-Desktop w/k8s enabled. Will be testing on other systems soon.

Additional Context

As with another issue I opened... I have been testing with private git repos via ssh for puppet-control, hiera, and most of the modules. Since all of this works on the initial deploy, it seems the repo/transport types are not factors.

[Xtigyro]

@slconley Thanks for contributing!

[slconley]

Glad to be helping... I should have a PR soon for some other stuff that is more straight-forward to me.