[PDB-announce] version 1.9.17 released

[Stefan Pratter]

Hi Mark,

Thanks for the feedback

During import from legacy data all erroring fields (incl. validation 
failures) are dumped into the notes field for investigative purposes, i 
haven't looked at this case specifically yet, but it sounds like the 
importer thinks the URL is invalid - if that is indeed a valid URL then 
it probably means the importer is too zealous during validation, i will 
make sure to look at it before the next update.

thanks!

On 28/09/15 11:26, Mark Tinka wrote:
> Hi Stefan.
>
> Many thanks for this, and for all your efforts in working on this.
>
> Just some feedback - the "Route Server URL" field is blank yet an 
> entry existing on the current platform. I'd imagine 2.0 would import 
> that current fields into the new platform, yes?
>
> That said, under the "Notes" field, "route_server:" appears with the 
> correct route server URL. So looks like the data is being picked up, 
> but being populated in the wrong place :-).
>
> You're welcome to use https://beta.peeringdb.com/net/3900 as an 
> example. Thanks.
>
> Mark.
>
> On 28/Sep/15 10:21, Stefan Pratter wrote:
>> version 1.9.17 has been released to beta.peeringdb.com
>>
>> =====================================================================
>>
>> WEB UI
>>
>>   * added 'Route Server URL' and 'Looking Glass URL' fields to 
>> network view
>>   * fixed bug where internet exchange view would show deleted prefixes
>>   * fixed bug where saving without making changes would cause link 
>> values to disappear from the main views
>>   * added re-captcha to signup process
>>
>> API / DATA
>>
>>   * This update contains some field and endpoint name changes so make 
>> sure to read this changelog carefully - we don't expect any 
>> additional name changes past this point.
>>
>>   * 'PATCH' method has been disabled until further notice
>>
>>   * 'version' field has been dropped from all serializers for the 
>> time being.
>>
>>   * /netix endpoint has been renamed to /netixlan
>>
>>   * sets will now be always named after the object type they are 
>> holding - this was already the case for most sets but some had to be 
>> renamed (see below)
>>
>>   * /net fac_set renamed to netfac_set
>>   * /fac net_set renamed to netfac_set
>>   * /ix fac_set now holds fac objects instead of ixfac objects
>>   * /ixlan prefix_set renamed to ixpfx_set
>>
>>   * ?depth parameter has been changed and now accepts a value
>>
>>     - /<obj>?depth=n
>>       * max depth: 2
>>       * depth: 0 dont expand anything (default)
>>       * depth: 1 expand all first level sets to ids
>>       * depth: 2 expand all first level sets to objects (original 
>> behaviour)
>>
>>     - /<obj>/<id>?depth=n
>>       * max depth: 4
>>       * depth: 0 dont expand anything
>>       * depth: 1-4 expand sets and related objects according to depth
>>
>>
>>   * /ixpfx endpoint added
>>     - this holds the same data as ixpfx_set under ixlan and may be used
>>       to update / create / delete prefixes using the appropriate methods
>>       (PUT, POST, DELETE)
>>     - can be queried by all fields existing on it's serializer as 
>> well as ix_id
>>   * /net field 'route_server' added
>>   * /net field 'looking_glass' added
>>   * /netixlan field 'is_rs_peer' added
>>   * /netixlan can now be queried by 'ix_id'
>>
>>   * dropped redundant ids from sets
>>     - /net netfac_set removed net_id
>>     - /net poc_set removed net_id
>>     - /net netixlan_set removed net_id
>>     - /ixlan ixpfx_set removed ixlan_id
>>     - /ix ixlan_set removed ix_id
>>     - /org net_set removed org_id
>>     - /org fac_set removed org_id
>>     - /org ix_set removed org_id
>> _______________________________________________
>> Pdb-announce mailing list
>> Pdb-announce at lists.peeringdb.com
>> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.peeringdb.com/pipermail/pdb-announce/attachments/20150928/f4a406b6/attachment.html>