Michael Ly

Ensure BIND9 config allows underscores

2

Ensure BIND9 configuration is set to allow zones with underscores ---- Good candidate files for changes: - Updates to BIND configuration: `/docker/bind9/etc/named.conf.local` The config option should be `check-names ignore;`

We currently allow users to submit IP addresses that are formatted as fully-qualified domain names (FQDNs) in CNAME record data, which is incorrect since mappings from a record name →...

Validate CNAME alias doesn't allow forward slashes for forward zones

2

We currently use the same validation regex for host names that we do for input names as we do CNAME data (including allowing of `/`). The issue is that only...

Improve out-of-sync record handling

9

### Background VinylDNS does not currently handle DNS requests well when the database differs from the source of truth (i.e. DNS backend). The current process is that users attempt to...

Possible duplicate records during concurrent zone sync

3

Under certain circumstances (eg. zone sync that is being processed multiple times), it is currently possible to have duplicate records.

Replace await with IO

1

**Motivation** Recently there have been some transient failures in our unit tests where the result of `await`/`awaitResultOf` will fail with a `None.get` exception. These should be replaceable using the Cats...

Ignore secret in ZoneConnection keys when stringifying

1

**Motivation** Sensitive connection information should be masked in the logs. Currently `ZoneConnection` doesn't have an override `toString` method to encrypt the connection information, so printing either the `ZoneConnection` or `Zone`...

Zones put endpoint doesn't utilize ID segment

1

**Bug description** Currently, the zone route for updating a zone is `/zones/:segment` where `:segment` is not used as all. We don't currently allow `PUT` requests at the `/zones` endpoint despite...

**Motivation** Tests in the `update_zone_test.py` currently use (and mutate) zone variables from `shared_zone_test_context` directly, but should ideally: 1. Use `get_zone` to retrieve the current zone 1. Perform the corresponding updates...

Clarification of behavior for "needs" and "name" tags in pipeline stage docs

2

**Background** When reading the example provided in the [pipeline stages `needs` documentation](https://github.com/go-vela/docs/blob/master/content/concepts/pipeline/stages/needs.md), it is not obvious that the stage name is used for the `needs` value rather than the stage...