Jamil d7be59707a fix(portal): Improve resource address validation (#8288) ...

We had a number of validation issues:

- DNS resources allow address `1.1.1.1` or `1.1.1.1/32`. These are not
valid and will cause issues during resolution.
- IP resources were allowing basically any string character on `edit`
caused by a logic bug in the changeset
- CIDR resources, same as above
- `*.*.*.*.google.com` and similar DNS wildcard resources were not
allowed

This PR beefs all of those up so that we have a higher degree of
certainty that our data is valid. If invalid data reaches connlib, it
will cause a panic.

This PR also introduces a migration to migrate any invalid resources
into the proper format in the DB.

Fixes #8287

2025-02-27 23:41:11 +00:00

..

api

fix(portal): Update gateway channel to process resource_update (#8280)

2025-02-27 01:46:13 +00:00

domain

fix(portal): Improve resource address validation (#8288)

2025-02-27 23:41:11 +00:00

web

fix(portal): Improve resource address validation (#8288)

2025-02-27 23:41:11 +00:00