-
Notifications
You must be signed in to change notification settings - Fork 52
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #241 from irrdnet/weak-refs-240
- Loading branch information
Showing
9 changed files
with
90 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
============================ | ||
Release notes for IRRd 4.0.3 | ||
============================ | ||
|
||
IRRd 4.0.3 was released on June 29th, 2019, and contains | ||
one change relating to referential integrity validation | ||
between RPSL objects. | ||
|
||
In earlier versions of IRRd, the `members` attribute of | ||
an `as-set`, along with several others, | ||
`were strongly validated`_. This meant it was not possible | ||
to add or update an `as-set`, if some of the members were | ||
not valid objects in the same source. The same applied | ||
to fields like `member-of` in a `route-set`. | ||
|
||
In IRRd 4.0.3, all references from `members`, `mp-member`, | ||
`mbrs-by-ref` and `member-of` are weak references. Their | ||
syntax is validated, e.g. for `as-set` members, values must | ||
be a valid `as-set` name or a valid AS number. However, there | ||
is no validation on whether the objects actually exist. | ||
It is also possible to delete e.g. a `route-set`, even when | ||
the object is still listed in the `member-of` in a `route` | ||
object, or to reference a maintainer that does not exist | ||
in a `mbrs-by-ref`. | ||
|
||
.. _were strongly validated: https://github.com/irrdnet/irrd4/pull/240 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,3 +6,4 @@ Release notes | |
|
||
4.0.1 | ||
4.0.2 | ||
4.0.3 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.