Bug #8509

Use puppet-git's tails Git repo in reprepro config generation script

Added by bertagaz 2015-01-01 16:48:33 . Updated 2019-08-22 10:59:01 .

Status:
Confirmed
Priority:
Low
Assignee:
Category:
Infrastructure
Target version:
Start date:
2015-01-01
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Reprepro scripts that need to fetch the main Tails git repo must use the one on puppet-git so that network troubles are handled at the git level and we don’t get annoyed by tons of emails when cronjobs fail.

This means passing another $git_remote parameter to the tails::reprepro::custom class, managing a SSH key pair with Puppet, and configuring Gitolite to give read-only access to that key.

Subtasks

History

#1 Updated by bertagaz 2015-01-01 16:50:26

  • Starter changed from No to Yes

Setting `easy` to `yes` because it doesn’t require any access to be able to patch the code.

#2 Updated by intrigeri 2015-01-01 17:30:22

> This means changing $git_remote in the tails::reprepro class.

No, this means passing a different value for the $git_remote parameter in our manifests. That’s what class parameters are for :)

#3 Updated by intrigeri 2015-01-01 17:31:49

  • Starter changed from Yes to No

bertagaz wrote:
> Setting `easy` to `yes` because it doesn’t require any access to be able to patch the code.

Well, no: the code is already generic enough, what needs to be done will be in our manifests (and gitolite config).

#4 Updated by bertagaz 2016-10-08 09:37:53

#5 Updated by intrigeri 2016-11-03 09:49:14

  • Subject changed from Use puppet-git tails repo in reprepro config generation script to Use puppet-git's tails Git repo in reprepro config generation script

#6 Updated by intrigeri 2019-08-22 10:59:01

  • Description updated