惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
The GitHub Blog
The GitHub Blog
Recent Announcements
Recent Announcements
A
About on SuperTechFans
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
U
Unit 42
WordPress大学
WordPress大学
Y
Y Combinator Blog
罗磊的独立博客
J
Java Code Geeks
Microsoft Azure Blog
Microsoft Azure Blog
腾讯CDC
博客园 - 叶小钗
Stack Overflow Blog
Stack Overflow Blog
Engineering at Meta
Engineering at Meta
Microsoft Security Blog
Microsoft Security Blog
GbyAI
GbyAI
V
V2EX
雷峰网
雷峰网
H
Hackread – Cybersecurity News, Data Breaches, AI and More
S
SegmentFault 最新的问题
酷 壳 – CoolShell
酷 壳 – CoolShell

External on CoreDNS: DNS and Service Discovery

JSON When Should Plugins be External?
Add External Plugins
miek · 2017-07-24 · via External on CoreDNS: DNS and Service Discovery

If you want to have your external plugin listed create a pull request.

In that pull request you’ll need to add a file to content/explugins/ that looks like this:

+++
title = "<plugin name>"
description = "*<plugin name>* is a ..."
weight = 10
tags = [  "plugin" , "<plugin name>" ]
categories = [ "plugin", "external" ]
date = "2017-07-22T12:37:19+01:00"
repo = "https://link-to-your-plugin-repo"
home = "https://link-to-your-homepage-or-readme"
+++

## Description

The *<plugin name>* plugin is a ...

## Syntax

## Example

See example.md for an example on how to do this.

Note that description needs to be a full sentence, and that repo must be a Go-gettable link that can be put in plugins.cfg.

Go Modules

Note we found the Go modules can interact badly with how external plugins are compiled into CoreDNS. Various external plugins have removed the go.mod and go.sum files entirely to work around issues, see for instance unbound.