Open
Milestone
started on Jan 1, 2023
Puppet CI
In 2023, we'd like to hook Puppet into CI. This can mean many things, but it will at least mean:
- server-side validation checks (team#31226 (closed), aka "you broke puppet here")
- deployment through a role account (team#29663 (closed))
- publish the puppet repository at long last (team#29387)
- puppet 7 server and agent upgrade (team#33588 (closed), team#40707 (closed), overlaps with %Debian 12 bookworm upgrade)
Ideally, we'd also be able to publish dynamic environments to test larger changes (team#40861 (closed)) and also, why not, actual unit tests in CI, although those are not mandatory here.
This is a smaller, more focused version of %cleanup and publish the sysadmin codebase which was too broad in scope, but that is kept to collect the dust on all that good wishful thinking.
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
11
- TPA team · allow agents to switch environments
- TPA team · Restructure Puppet repository
- TPA team · TPA-RFC-76: mirror tor-puppet.git to the gitlab server
- TPA team · cleanup branches in tor-puppet.git
- TPA team · deploy dynamic environments on the Puppet server
- TPA team · add validation checks in puppet
- TPA team · Remove stale Puppet development environments automatically
- TPA team · switch from librarian to g10k
- TPA team · migrate to puppetserver and Puppet agent 7 before EOL
- TPA team · Deploy /etc/puppet as a role account
- TPA team · upgrade the PuppetDB package or find a replacement
Loading
Loading
Loading