Re: JSON based API to query available AMIs
> toolchain? If you can generate the static JSON file at each AMI
> generation / upload, I can then investigate with the www.d.o team how to
> publish it on www.d.o natively, if feasible there, or where else it
> should go.
Shouldn't be a problem, but I am not sure how the procedure of
replicating the AMIs across regions work.
It might be out of the scope of the bootstrapper to generate the full
JSON object.
If we could automate the replication across regions and the publishing
process, then yes; we could generate the whole document.
Anders
On 24 November 2012 11:35, Stefano Zacchiroli <zack@debian.org> wrote:
> [ adding the bug log to Cc, to keep track of relevant information ]
>
> On Thu, Nov 22, 2012 at 10:52:46PM -0800, Eric Hammond wrote:
>> >The JSON format you mentioned looks reasonable. However, this brings us
>> >back to the infrastructure question: we'll need to host a corresponding
>> >CGI (or whatever it is that implements the query service) somewhere.
>> >Where?
>>
>> Even though I called it an "API", you probably could implement this as
>> static JSON files without any CGI or dynamic calculations.
>
> Right, very good point.
>
>> Every time you publish new AMIs, write new static JSON files with the
>> latest ids.
>
> Anders, James, do you think this is easy to integrate in the AMI build
> toolchain? If you can generate the static JSON file at each AMI
> generation / upload, I can then investigate with the www.d.o team how to
> publish it on www.d.o natively, if feasible there, or where else it
> should go.
>
> TIA,
> Cheers.
> --
> Stefano Zacchiroli . . . . . . . zack@upsilon.cc . . . . o . . . o . o
> Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
> Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o .
> « the first rule of tautology club is the first rule of tautology club »
Reply to: