[ncc-services-wg] [db-wg] RIPE Database Release 1.69 Available Now

Dear Aris

This was a small change that we implemented quite some time ago. It was 
not included in previous releases and added into the latest which is 
probably why we missed it in the release notes.

We had previously announced the change in the 'DIFF' implementation with 
this now being the default behaviour. We were asked at the last RIPE 
Meeting for this dry-run behaviour.

If it is still considered useful to have a subject line keyword to 
trigger a dry-run we can change it to a new keyword (DRY-RUN) on the 
next release.

Regards
Denis Walker
Business Analyst
RIPE NCC Database Team


On 01/10/2013 13:03, Aris Lambrianidis wrote:
> Thanks for the explanation Denis!
>
> Perhaps it'd be prudent to clarify that somewhere on the website. In
> my mind the deprecated use of the DIFF keyword was a completely
> separate issue from the dry-run option, as those modifications as to
> how objects are parsed were done at different points in time.
>
> Plus, the warnings and errors produced are not as helpful, there's
> the (standard) warning about using the DIFF keyword and then an error
> about "dry-run being  supported only when a single object is
> specified".
>
> Kind regards,
>
> Aris Lambrianidis AMS-IX B.V. Tel.+31  (0)6 23 59 41 58
> http://www.ams-ix.net/
>
>
>
>
> On Oct 1, 2013, at 12:51 , Denis Walker <denis at ripe.net> wrote:
>
>> Dear Aris,
>>
>> If you use the keyword 'DIFF' in a subject line of an email update
>> the software will treat the update as a dry-run and does not handle
>> multiple objects.
>>
>> There is no need to use 'DIFF' as a keyword to get a diff output.
>> By default all notification messages for object modifications now
>> return the diff output followed by the full new object.
>>
>> Regards Denis Walker Business Analyst RIPE NCC Database Team
>>
>>
>> On 01/10/2013 12:34, Aris Lambrianidis wrote:
>>> Hello Denis and all,
>>>
>>> Any chance the new feature broke multiple object updates via a
>>> single email (without using the dry-run option, ofc.)? We seem to
>>> be getting error messages when trying to do that, I've already
>>> notified auto-dbm@ about it.
>>>
>>> Aris Lambrianidis AMS-IX B.V. Tel.+31  (0)6 23 59 41 58
>>> http://www.ams-ix.net/
>>>
>>> On Sep 23, 2013, at 15:50 , Denis Walker <denis at ripe.net> wrote:
>>>
>>>> Dear colleagues,
>>>>
>>>> Release 1.69 of the RIPE Database has now been fully deployed.
>>>>
>>>> Regards,
>>>>
>>>> Denis Walker Business Analyst RIPE NCC Database Team
>>>>
>>>>
>>>>
>>>>
>>>> -------- Original Message -------- Subject: [db-wg] RIPE
>>>> Database Release 1.69 Available Soon Date: Mon, 09 Sep 2013
>>>> 15:27:50 +0200 From: Denis Walker <denis at ripe.net>
>>>> Organization: RIPE NCC To: Database WG <db-wg at ripe.net>, NCC
>>>> Services WG <ncc-services-wg at ripe.net>
>>>>
>>>> Dear colleagues,
>>>>
>>>> The RIPE NCC is pleased to announce that we have deployed a
>>>> new release of the RIPE Database to the TEST Database
>>>> environment. Detailed information about the new release,
>>>> including dates and information about the changes can be found
>>>> here:
>>>> https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.69
>>>>
>>>>
>>>>
>>
>>>>
Of special note in this release is the inclusion of "dry-run". Using the
>>>> dry-run function you can test whether an update would succeed
>>>> or not. The update procedure runs as normal except that no
>>>> change is made to the database. Find out more about the dry-run
>>>> function here:
>>>> https://labs.ripe.net/Members/denis/dry-run-testing-in-the-ripe-database
>>>>
>>>>
>>>>
>>
>>>>
Due to recent issues with the REST API, we've extended the migration
>>>> period up until the 1.70 release. This release is currently
>>>> scheduled for the end of October.
>>>>
>>>> If you have any questions or comments, we look forward to
>>>> hearing them!
>>>>
>>>> Regards,
>>>>
>>>> Denis Walker Business Analyst RIPE NCC Database Team
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>