Add the IX-F Member Export URL to the ixlan API endpoint

[arnoldnipper]

1. if you want to automate and process, the API is the only way to do this

2. all information which is in the user GUI should also be accessible via the API

[grizz]

One of the problems with this is that some IXPs don't want the list being public I believe.

I'm for this if we also add a tick box for import_url_is_public or something.

@peeringdb/pc thoughts?

[arnoldnipper]

+1 ... however, this information is public via "curl -sGL https://api.ixpdb.net/v1/provider/list | jq -r -c '.[] | select (.apis.ixfexport != "") | .apis.ixfexport'" atm

[shane-kerr]

So is the proposal to first to add a tick box specifying whether an IXP to allow listing members publicly, right? That creates several questions:

• What should the default be on creation (I guess default to open to mimic current behavior, but opinions may vary)?
• What should we set existing IXP to for this value (again, probably open)?
• Do we need to somehow alert IXP that this is now an option? (A simple way would be contacting mentioning this in release notes, but that is basically a CYA approach. A better way would be e-mail. The "best" way might be to make a table containing all IXP that have not yet chosen a value and alerting them when they use the GUI.)

Then once this option is added, we have two additional tasks:

1. Create an API call like requested in this ticket initially.
2. Update the GUI to respect the new option.

Does that cover it?

[arnoldnipper]

• The default should be "no" to reflect the existing behaviour
• for existing IX-F imports, visibility should be set to "no"
• An email to announce should do. No need to contact IXes individually

[grizz]

+1 ... however, this information is public via "curl -sGL https://api.ixpdb.net/v1/provider/list | jq -r -c '.[] | select (.apis.ixfexport != "") | .apis.ixfexport'" atm

There may be a case that an IXP would share it privately with PDB, but still not expose it to the public. At least I think, am I wrong in that assumption?

[grizz]

• The default should be "no" to reflect the existing behaviour
• for existing IX-F imports, visibility should be set to "no"
• An email to announce should do. No need to contact IXes individually

Agree.

Then once this option is added, we have two additional tasks:

1. Create an API call like requested in this ticket initially.
2. Update the GUI to respect the new option.

Does that cover it?

Yep, 1 will happen automatically just by creating the new the field, so it will just be 2.

[arnoldnipper]

Would you mind to summarize and to call for voting, @grizz ... afais this issue has already support from @shane-kerr @grizz and @arnoldnipper

[grizz]

@arnoldnipper sure

• An email to announce should do. No need to contact IXes individually

By this, you mean just a standard new version with X features to pdb-announce, right?

[arnoldnipper]

By this, you mean just a standard new version with X features to pdb-announce, right?

Right, @grizz

[grizz]

Add two new fields to the API:

• ixf_import_url string for the URL to fetch
• ixf_import_url_visible string for visibility the same as the current poc records: public, users, private

ixf_import_url_visible will default to private which means it will only display for users who are members of the org

@peeringdb/pc slight change to the visibility to keep it in line with poc records

[arnoldnipper]

+1 for what @grizz proposed

[grizz]

@peeringdb/pc need another vote please

[arnoldnipper]

@grizz, I see support from you, @shane-kerr and me. That's three. How many do we need?

[ynbrthr]

here is another one: +1

[koalafil]

Can we pls have the Release Notes? Thx.

[koalafil]

@arnoldnipper Release Notes pls

[vegu]

This was specified to add the following fields ixf_import_url and ixf_import_url_visible

However the url field is already exposed on the API for POST and PUT requests as ixf_ixp_member_list_url, in order to allow people to set it.

For consistency the visibility field will be named ixf_ixp_member_list_url_visible as well.

In summary, the fields available on the api will be ixf_ixp_member_list_url and ixf_ixp_member_list_url_visible

[arnoldnipper]

Release Notes
There are two new fields in the ixlan section resp. the ixlan object, called ixf_ixp_member_list_url and ixf_ixp_member_list_url_visible. The first one contains the URL to the IX-F import file while the second governs the visibility of the URL. Values are the same as for the poc object, namely "Public", "Users" and "Private", defaulting to "Private" (i.e. or users who are members of the org)