Poweradmin\Application\Service\Record\RecordEditRequest

final class RecordEditRequest (View source)

One record edit as the edit-record form or an API PUT submits it. The caller has already found and authorised the stored row; the service normalises the submitted values and writes.

Methods

__construct(int $zoneId, string $zoneName, int|string $recordId, array $current, string $name, string $type, string $content, int $ttl, int $prio, int $disabled, string|null $comment, bool $syncPtr, bool $bumpSoaSerial, int $userId, string $username, string $origin = AuditLoggerInterface::ORIGIN_WEB, Closure|null $ptrZoneAllowed = null)

No description

Details

at line 48
`__construct(int $zoneId, string $zoneName, int|string $recordId, array $current, string $name, string $type, string $content, int $ttl, int $prio, int $disabled, string|null $comment, bool $syncPtr, bool $bumpSoaSerial, int $userId, string $username, string $origin = AuditLoggerInterface::ORIGIN_WEB, Closure|null $ptrZoneAllowed = null)`

No description

Parameters

int	$zoneId
string	$zoneName
int\|string	$recordId	Numeric id, or the encoded identifier of an API-backed record
array	$current	The stored row being edited (name, type, content, ttl, prio)
string	$name
string	$type
string	$content
int	$ttl
int	$prio
int	$disabled
string\|null	$comment	The record comment to store, or null to leave comments as they are (a rename then only carries an existing comment along)
bool	$syncPtr	Move the PTR of an A/AAAA record along with the edit
bool	$bumpSoaSerial	The web form lets an SOA carry a serial placeholder whose expanded value is bumped after the write (#1360); API callers keep the serial they sent and pass false
int	$userId	The acting user; a synced comment reaches only zones this user may edit
string	$username
string	$origin	One of the AuditLoggerInterface::ORIGIN_* values; the API writes api_edit_record
Closure\|null	$ptrZoneAllowed	Whether the caller may write the synced PTR into its reverse zone (an API key's zone scope)