Paths

Table of Contentst

Allow Docker containers to use ACME DNS API
ClosedPublic
Actions

Authored by dereckson on Feb 4 2020, 22:53.

Tags

None

Referenced Files

	Unknown Object (File)
	Fri, Jul 25, 15:47

	Unknown Object (File)
	Tue, Jul 22, 02:52

	Unknown Object (File)
	Mon, Jul 21, 05:57

	Unknown Object (File)
	Mon, Jul 21, 05:57

	Unknown Object (File)
	Mon, Jul 21, 01:12

	Unknown Object (File)
	Sat, Jul 19, 05:21

	Unknown Object (File)
	Sat, Jul 19, 02:07

	Unknown Object (File)
	Tue, Jul 15, 07:58

View All Files

Subscribers

None

Details

Reviewers

dereckson

Commits

rOPS954b73ae74db: Allow Docker containers to use ACME DNS API

Summary

On the Docker engines, the certbot command is run as a container,
and so doesn't use public IP.

This is a follow-up for efa09f17.

Test Plan

Tested on Equatower with D2181.

Diff Detail

Repository

rOPS Nasqueron Operations

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

dereckson requested review of this revision.Feb 4 2020, 22:53

dereckson created this revision.

Harbormaster completed remote builds in B3386: Diff 5491.Feb 4 2020, 22:53

dereckson accepted this revision.Feb 4 2020, 22:53

This revision is now accepted and ready to land.Feb 4 2020, 22:53

Closed by commit rOPS954b73ae74db: Allow Docker containers to use ACME DNS API (authored by dereckson). · Explain WhyFeb 4 2020, 22:56

This revision was automatically updated to reflect the committed changes.

dereckson added a commit: rOPS954b73ae74db: Allow Docker containers to use ACME DNS API.

Revision Contents
Changeset List

Path

Size

roles/

paas-docker/

nginx/

files/

includes/

geo_nasqueron

3 lines

Diff 5492

View Options

roles/paas-docker/nginx/files/includes/geo_nasqueron

Allow Docker containers to use ACME DNS APIClosedPublicActions