Add Record-Level API

Open
#540 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 14 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start by comparing the proposed POST and DELETE record-level endpoints with the existing RR-set API. Resolve the stated concerns about DELETE request payloads and larger transactions; done means the API behavior and its transaction semantics are decided and documented.

Written by the indexing model from the issue text.

Description

api enhancement prio: medium

An idea how to add records to an existing RR set could be like this:

POST desec/example.com/rrsets/www/A/records/

[
"1.2.3.4",
"4.3.2.1"
]

To delete some records,

DELETE desec/example.com/rrsets/www/A/records/

[
"1.2.3.4"
]

could be used.

Some clients may have trouble with DELETE request that contain payload (but that's actually allowed).

Another issue may be that this cannot be done within a larger transaction.

Dominant language
Python
Stars
678
Forks
74
Avg merge
7d 23h
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from desec-io/desec-stack

All issues in desec-io/desec-stack

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.