[ixpmanager] ixf-id mandatory for json export

[Barry O'Donovan (INEX)]

Hey Nishal,

that's less an IXP Manager requirement and more a requirement of the schema:

https://github.com/euro-ix/json-schemas/blob/master/ixp-member-list.schema.json#L30


There is a workaround for use-cases where you may not have one:

First option - tack the following to the URL: ?ignore_missing_ixfid=1

The second is to set one as part of the request:

?ixfid_n=m

where n is the IXP ID in the schema (this if infrastructure.id in the 
IXP Manager database - usually 1 for most) and m is what you want the 
ixf_id to be.

  - Barry




Nishal Goburdhan via ixpmanager wrote on 02/05/2023 09:43:
> 
> hi,
> 
> it appears that an ixf-id is now mandatory to generate the json export from ixpmanager.
> i can grok why this might be _desirable_;  which, iirc, was the previous/legacy case with ixpmanager.
> but, i don’t believe it should be _mandatory_;  especially if the IX has a peeringdb id (ie. that which is actually useful!)
> 
> how to get this made optional again (without inserting a random number into the database, or making other code hacks)
> 
> -n.
> 
> (who has been waiting a week to get an id-that-he-doesn’t-feel-he-really-needs-and-has-never-had-to-apply-for-before allocated)
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager
> 


-- 

Kind regards,
Barry O'Donovan
INEX Operations

https://www.inex.ie/support/
+353 1 531 3339