# Porkbun provider

The [Porkbun](https://porkbun.com) provider implements all
[Protocol53](https://github.com/outskirtslabs/protocol53) operations with
Porkbun’s v3 API.

## Installation

```clojure
{:deps {com.outskirtslabs/protocol53-porkbun {:mvn/version "0.0.1"}}}
```

## Authentication

Enable API access for the Porkbun account and each domain the provider should
manage, then create an API key and secret key.

```clojure
(require '[ol.protocol53.porkbun :as porkbun])

(def dns
  (porkbun/provider {:api-key    "pk1_..."
                     :secret-key "sk1_..."}))
```

Pass a caller-built `java.net.http.HttpClient` as `:http-client` when advanced
HTTP policy requires Java interop.

## Record Behavior

Porkbun derives its minimum record TTL from account settings; 600 seconds is
the typical floor. The provider raises lower requests to 600, then rereads the
zone after append and set operations so it returns the TTL Porkbun actually
stored. MX and SRV priorities are translated between Protocol53’s portable
record data and Porkbun’s separate `prio` field.

## Integration Tests

<dl><dt><strong>⚠️ WARNING</strong></dt><dd>

Run the lifecycle suite only against a dedicated disposable zone. It creates,
replaces, and deletes DNS records whose effective owner starts with
`p53test-`.
</dd></dl>

Set these variables in the process environment or the repository `.env` file.
Process values take precedence over `.env` values.

|     |     |     |
| --- | --- | --- |
| Variable | Required | Description |
| `PORKBUN_API_KEY` | yes | Porkbun API key with access to the test domain. |
| `PORKBUN_SECRET_KEY` | yes | Secret key paired with the API key. |
| `PORKBUN_DOMAIN` | yes | Dedicated zone, with or without a trailing dot. |

Run the Porkbun lifecycle suite from the repository root:

```shell
bb test:integration --provider porkbun
```

The wrapper ignores TTL differences because Porkbun applies the test account’s
minimum to fixture TTLs. Do not run concurrent lifecycle suites against one
zone.