1225693 - [product-details] Please add regions data to product-details.mozilla.org

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)

Description

[Paul [:pmac] McLanahan]

This service (product-details.m.o) has just been setup by ericz for data from ship-it in bug 1146897. Clients that use those data files also expect a folder called "regions" to exist containing the translated country names of the world. This is info extracted from Firefox itself and maintained in svn:

http://svn.mozilla.org/libs/product-details/json/regions/

Please setup a script that will sync the regions data in the above link to:

https://product-details.mozilla.org/regions/

These files change very infrequently, so one daily sync will be fine.

Comment 1

[Eric Ziegenhorn :ericz]

Is there a non-html listing of the json region files to pull?  I'll do some fancier parsing in python if necessary but already have a bash script for a simpler approach.

Comment 2

[:Atoll]

Should we just do 'svn co svn+ssh://<path>/to/json/regions/' and then put an svn update; deploy somewhere?

Comment 3

[Paul [:pmac] McLanahan]

(In reply to Eric Ziegenhorn :ericz from comment #1)
> Is there a non-html listing of the json region files to pull?  I'll do some
> fancier parsing in python if necessary but already have a bash script for a
> simpler approach.

Not that I'm aware of. django-mozilla-product-details gets the file list with a very simple parse of the HTML:

https://github.com/mozilla/django-product-details/blob/master/product_details/management/commands/update_product_details.py#L116

(In reply to Richard Soderberg [:atoll] from comment #2)
> Should we just do 'svn co svn+ssh://<path>/to/json/regions/' and then put an
> svn update; deploy somewhere?

That will work fine too. Eventually we'll have to move these files somewhere else (likely github) since apparently svn.m.o will be going away, but it'll be easy to update this when that happens. We're already discussing it in bug 1225359.

Comment 4

[:Atoll]

We have lots of websites driven by either svn or git repo commits, so that shouldn't be a big issue.

Comment 5

[Sylvestre Ledru [:Sylvestre]]

Eric, as I think this should be discussed before working on an implementation, how are you planning to manage that? Thanks

Comment 6

[Eric Ziegenhorn :ericz]

Feel free to discuss.  The svn approach sounds more resilient and easier to adapt to a post-svn world to me.

Comment 7

[Paul [:pmac] McLanahan]

(In reply to Eric Ziegenhorn :ericz from comment #6)
> Feel free to discuss.  The svn approach sounds more resilient and easier to
> adapt to a post-svn world to me.

Agreed. Switching from svn to git whenever it happens should be very straight-forward.

Comment 8

[Eric Ziegenhorn :ericz]

svn approach has been implemented.  It updates once a day.  If another approach has more merit, we can switch.