switch from librarian to g10k
in #40861 (comment 3142097), we agreed we'd use g10k to manage third-party repositories, let's do it.
i have hooks locally to do this.
specifically, the proposal is what @lavamind wrote in wiki-replica@467aa42c
i think the next steps are:
- locally, delete all of
3rdparty/modules
- run
cd 3rdparty && g10k -puppetfile -moduledir modules/
to repopulate the directory - check that the actual checkout is unchanged, or audit if changes are okay (e.g. metadata from tarballs might have been removed, that's fine)
- pin all checksums in the Puppetfile, either with the checksum of the tarball or a git commit, see my puppetfile for an example,
might be possible to extract this from the lock filenope, lock files don't have checksums - rerun g10k, check git status, should be a noop
- delete
3rdparty/modules
from git, for real
The above should be done in a branch, most likely.
Once that's done, the branch is ready to be deployed on the server. The server needs to be configured to deploy 3rdparty modules to the right location. I'm not sure how that works with environments, but I'm using this hook to run g10k, essentially only if the Puppetfile is changed.
@lavamind, i can do the git branch, could you see how to integrate g10k on the server side?
feel free to reassign to me after checking.
To do
- switch from librarian to g10k
- fix notifications and branch protection
- move pauli back to the production environment
-
switch
tor-puppet-hiera-enc.git
to also use theproduction
branch -
notify
tpa-team@
about the switch - check if doc needs updating