Page MenuHomePhabricator

Remove old letsencrypt puppet module
Closed, ResolvedPublic

Description

<bblack> (can we kill the old letsencrypt module yet?)

Conditional:

  • modules/tlsproxy/manifests/localssl.pp - this is probably only used in beta, which is using acme-chief from cherry-picks - please merge changes listed at T182927#5087304
  • modules/profile/manifests/gerrit/server.pp - @Paladox who does not have acme-chief installed

Unconditional:

  • modules/archiva/manifests/proxy.pp - see change below
  • modules/profile/manifests/mail/smarthost.pp - used on the mx-out hosts in cloudinfra, no acme-chief installed but that could be done
  • modules/profile/manifests/toolforge/mailrelay.pp - tools project, no acme-chief installed but that could be done
  • modules/toolserver_legacy/manifests/init.pp - toolserver-legacy project, no acme-chief installed but that could be done

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
This comment was removed by Krenair.

I use " modules/profile/manifests/gerrit/server.pp: letsencrypt::cert::integrated { 'gerrit':" for gerrit.git.wmflabs.org and gerrit.gerrit.wmflabs.org as the acme service does not work in WMCS. (Or the last time i checked it didn't work).

It does work in Cloud VPS, with some puppet cherry-picks and some credentials permitted by WMCS admins to allow modification of designate DNS records from within instances.

Change 504648 had a related patch set uploaded (by Alex Monk; owner: Alex Monk):
[operations/puppet@production] archiva::proxy: remove old letsencrypt module stuff

https://gerrit.wikimedia.org/r/504648

Change 504648 merged by Vgutierrez:
[operations/puppet@production] archiva::proxy: remove old letsencrypt module stuff

https://gerrit.wikimedia.org/r/504648

BBlack subscribed.

The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all tickets that aren't are neither part of our current planned work nor clearly a recent, higher-priority emergent issue. This is simply one step in a larger task cleanup effort. Further triage of these tickets (and especially, organizing future potential project ideas from them into a new medium) will occur afterwards! For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!